Five steps. One number. No surprises anywhere in it.
Most studios describe their process in adjectives. Here is ours in specifics: what happens at each step, what you have to do, what exists at the end of it, and how long it takes. If a step cannot answer all four, it is not a step, it is a delay.
The engagement // Start to keys
Nothing here happens in a room you are not in.
- 0101Answered inside one business day
The inquiry
You write. A person answers.
Tell us the business, the problem, and what a good outcome looks like. Detail helps, and so does telling us what you already tried and why it did not stick. Every inquiry gets read and answered, including the ones that are not a fit, because a fast no is worth more to you than a slow maybe.
- Your part
- One honest note. What you have tried already is the useful part.
- What exists after
- A straight answer on fit, and the first question worth arguing about.
- How long
- Answered inside one business day
- 0202One hour, usually within the week
The working session
Not a sales call. A working hour.
We take your problem apart on a call and put it back together with fewer pieces. What the business actually needs, what it does not, and what has to be true for this to be worth doing. Most of the hard thinking on an engagement happens here, before anyone is paid.
- Your part
- An hour, and the willingness to be told the answer is smaller than you thought.
- What exists after
- An agreed outcome, the constraints around it, and what to build first.
- How long
- One hour, usually within the week
- 0303Within 48 hours of the session
The proposal
One number, in writing, that does not move.
A written scope with a set package price, a fixed timeline, the milestones, and an explicit list of what is out. The out list is the important half: it is how you know the price is real rather than a guess with room to grow.
- Your part
- Read it properly and push on anything that reads vague. That is what it is for.
- What exists after
- A scope, a price, a date, and a list of what this is not.
- How long
- Within 48 hours of the session
- 0404Days to weeks, fixed in the proposal
The build
You watch it happen, in the open.
Work starts on the agreed date and you can see it from the first day. A weekly written update, a live link the moment there is something to look at, and a standing invitation to say when something is wrong while it is still cheap to change.
- Your part
- Look at it when we send it, and tell us the truth about what you see.
- What exists after
- A working thing on a real URL, getting closer every week.
- How long
- Days to weeks, fixed in the proposal
- 0505Launch day
The handoff
You leave owning all of it.
The repository, the live deployment, the domain, every account and credential, and the documentation to run it without us. Not a licence and not a lease. If you hired another engineer tomorrow they could pick it up, which is the only real test of whether you own something.
- Your part
- Accept the transfer, and keep the credentials somewhere you will find them.
- What exists after
- The asset, in your name, with the keys.
- How long
- Launch day
The terms // The same for everybody, every time
These are not values. They are the deal.
Every one of these is something you could hold up later and point at. That is the only kind worth printing.
One price, agreed before anything is built
A set package price for a defined scope, in writing, before work starts. You see the whole cost and the whole delivery date up front, and the number is the number.
Changes are included, permanently
Adjustments to what we built are included, forever. No change order, no second invoice, no conversation about whether it counts. Work that adds something we never agreed to build is a new engagement, quoted the same way as the first.
You own everything
Code, deployments, domain, accounts, credentials. Transferred to you, not licensed. There is no seat fee, no platform you are stuck on, and nothing you have to keep paying us to keep using.
Straight through, start to finish
No coordination tax and no telephone game. The people who scope your engagement are the people who build it, so nothing gets lost being explained a second time.
We finish the work
We do not stop at a handoff date. We stop when the thing is right by you. Revisions are inside every engagement rather than bolted on, which is why there is nothing to refund and nothing to argue about.
Stewardship over extraction
Every decision gets made for the version of your business that exists in three years. We build assets you own and can operate without us. We do not build dependency, and we will tell you when something is not worth building at all.
The number // How it gets arrived at
There is no price list, and that is not coyness.
A focused site for one town and a full operating system with booking, a store, and a back office are not the same piece of work, and pricing them as though they were only ever serves the one that is cheaper to build.
So the quote comes after the working session, when we both know what is actually being made. It is one set package price for a written scope, it is agreed before anything is built, and it does not move afterwards.
Where to start
Start with the audit, not the sales call.
Sixty seconds, no card. It names the one thing quietly costing you the most, and the answer is yours to keep whether or not we ever work together. Most engagements begin there, because it is easier to decide what to build once you can see what is leaking.
Run the free auditFit // We say no early, and out loud
A fast no is worth more than a slow maybe.
- You run something real, with revenue and customers, and you want it to work better.
- You would rather hear a hard no early than a soft yes that costs you a quarter.
- You want to own what gets built, and you understand why that matters.
- You can say what a good outcome looks like, even roughly.
- You are shopping for the cheapest quote. We will lose that one on purpose.
- You want a strategy deck. The work here is the deliverable, not a document about it.
- Eight people have to approve a button colour.
- You want agentic systems in the business because a competitor announced some.
Straight answers // No sales call required
Questions, answered plainly.
How does pricing work?
Every engagement is scoped in one working session and quoted privately as a set package price, agreed in writing before anything is built. You see the whole cost and the whole timeline before work starts and the number does not move afterwards. There is no price list on this site because a focused site and a full operating system are not the same piece of work.
Where do most people start?
With the free audit, usually. It takes sixty seconds, it names the one thing quietly costing you the most, and you keep the answer whether or not you ever hire us. Most engagements begin there rather than with a sales conversation, because it is easier to decide what to build once you can see what is leaking.
How fast does it go live?
A focused website or a voice agent is typically live within a week or two of kickoff. Custom applications, stores, and deeper software usually run two to six weeks. Whole-operation engagements run longer because they cover more of the business. The exact date is in your proposal, next to the price, before you agree to either.
Do you offer payment plans?
Yes. Most engagements can be split into milestone payments that fit your situation. Say so in the working session and we structure it together before the proposal is written.
Who owns the code and the accounts?
You do, fully, and from day one rather than at the end. Code is delivered to your repository. The domain, the hosting, the database, and every credential are in your name. There is no licence, no seat fee, and nothing you have to keep paying us to keep using.
What if I am not happy with what gets built?
We do not work in handoffs, we work in iterations, and we do not stop until it is right by you. Revisions are inside every engagement rather than bolted on. There is nothing to refund because we do not walk away from unfinished work.
I do not know much about agentic systems. Is this still for me?
Yes, and most clients do not. A website or a voice agent asks nothing of you technically, and a custom build starts with working out what to build together. You bring the business and the judgment about your own customers. We bring the technical decisions and we explain the ones that matter.
What if my project does not look like anything on your site?
Plenty do not, and that is usually the interesting ones. Say what you are trying to make happen rather than what you think it should be called. The working session exists to turn that into a scope.
Step one · Answered inside one business day
Tell us what you are building.
The business, the problem, and what a good outcome looks like. You will get a straight answer on fit, whether or not it is one.
Kalispell, Montana. Working with clients nationwide.