FAQ
Questions, answered.
The things people usually want to know before they reach out. If you don't see yours, just ask. We're easy to talk to.
Getting started
How do we start working with you?
Send us a few sentences about what you're working on through the contact form. We'll get back to you within a business day to set up a call. There's no obligation and no hard sell. We usually start with a short discovery phase so we know we're solving the right problem before anyone writes code.
Do we need to have everything figured out first?
No. Plenty of our projects start with "here's what's broken, help us figure out the rest." A rough idea is enough to get the conversation going. Turning a vague problem into a clear plan is part of the work.
What does working with you actually feel like?
We work in four stages: we get the lay of the land, agree on a plan, build it, and hand it over. You see working software early and you're involved the whole way, so there's no big mysterious reveal at the end.
Pricing and timelines
How much does it cost?
It depends on the scope and the type of work, so we don't quote from a price sheet. After a short discovery conversation we send you a written proposal that spells out the work and the cost up front. You won't get a surprise invoice.
How long do projects usually take?
It ranges from a few weeks to several months, depending on what you need. We'd rather ship something useful early and improve it than disappear for a quarter and hope it lands. You'll get an honest timeline during discovery, not a hopeful one just to win the work.
What kinds of engagements do you offer?
Three main types. Project work is a defined build with a clear outcome. A retainer gives your team ongoing capacity. Advisory is senior guidance and oversight, often part time. If you're not sure which fits, that's one of the first things we'll help you sort out.
What we do and who we work with
What do you actually do?
We help with technology strategy, building software, data and AI, cloud and infrastructure, cleaning up operations, and part-time technical leadership. The common thread is taking an idea and turning it into software that works, and sticking with it from start to finish.
What kind of companies do you work with?
Companies with a real problem who want a senior partner to help solve it. That's often founders, growing startups, and established teams trying to modernize older systems. If you're somewhere between "we know something's wrong" and "we know exactly what to build," you're in the right place.
Do you really do AI, or is that just on the brochure?
We build real AI features, like data pipelines and tools that use language models to do something useful, not demos that only look good in a screenshot. We're also happy to tell you when AI isn't the right answer for what you're trying to do.
We have a messy legacy system. Is that a dealbreaker?
It's a lot of what we do. Untangling and gradually replacing an aging system without bringing the business to a halt is right up our alley. The messier it feels to you, the more useful we usually are.
What if our project doesn't fit neatly into one of your services?
Most don't, and that's fine. Those categories are a starting point, not a fixed menu. Tell us the problem in your own words and we'll tell you honestly whether we're the right people to solve it.
Logistics
Where are you based, and do you work remotely?
We're based in Morgantown, West Virginia, and we work remotely with clients anywhere. Most of the work happens over the tools your team already uses, and we fit around your time zone rather than the other way around.
How quickly will you get back to us?
Within one business day for any message. Once we're working together, we keep you updated regularly so you always know where things stand without having to chase us for it.
Ownership and trust
Who owns the code and the IP?
You do. Everything we build is yours, handed over with documentation and tests so your team can run it and grow it long after we're gone. We don't lock you in.
What happens when the engagement ends?
We plan for the handoff from the start. By the end you'll have systems you understand, documentation that's actually useful, and what you need to run things without us. If you want us to stay on for advice, we're glad to, but that's your choice, not something we build in.
Can we trust you with sensitive or confidential information?
Yes. We treat your data, plans, and code as confidential, we're glad to sign an NDA before we start, and we build security in from the beginning instead of adding it at the end.
Still wondering about something?
If your question isn't here, that probably means it's a good one. Tell us what's on your mind and we'll get back to you within one business day.
Ask us anything