Six steps.
No surprises.
This is exactly how a build runs, start to finish, for a BC business or public body commissioning software instead of renting it. One fixed price. Working software at every check-in. The code in your name at the end.
- 06
- Steps, end to end
- 1 day
- First written reply
- $0
- Cost to find out
- 100%
- Code and IP to you
From first email to handover.
Six discrete steps. Each one ends with something concrete you can look at and approve before the next one starts.
How long the whole thing takes depends on scope. A focused automation is a matter of weeks. A system that runs an operation is staged into milestones, and the schedule is written into the proposal before you sign it rather than discovered along the way.
- STEP 01
Free teardown
You describe how the business actually runs, and we come back with pointed questions about the tools you pay for, where work falls through the cracks, and what people are doing in spreadsheets because the software will not. Within one business day you get a written summary of what we found, what we would build, and which of your current tools we think you should keep renting. It costs nothing, there is nothing to sign, and there is no call to schedule first.
- STEP 02
Scope and one fixed quote
We define exactly what gets built, what it does on day one, what it deliberately does not do yet, and what it costs. You get a single fixed number, not a range and not an hourly rate. If paying it up front is the obstacle, this is where we structure it over two years at roughly what you already spend on the subscriptions it replaces.
- STEP 03
Agreement and kickoff
Sign, and work starts inside a week. You talk directly to the person building your software. There is no account manager in the middle relaying requirements, and no discovery phase that bills for six weeks before anything runs.
- STEP 04
Build, in milestones you sign off
Work is broken into milestones with a regular check-in on each one. At every check-in you see working software, not slides and not a status report. Billing follows the milestones, so nothing is invoiced for work that has not shipped. Changes get caught while they are cheap instead of after launch.
- STEP 05
Your people test it on real work
Before anything goes live, the people who will actually use it run their real workflows through it. What they find gets fixed. Revisions inside the agreed scope are not nickel-and-dimed, because a build that technically matches the spec but does not fit the job is not finished.
- STEP 06
Migration and handover
We move the data and check it against the old system. Nobody on your side should spend more than about fifteen minutes getting set up: a new login, a new password, and back to work. At handover you receive the full codebase, the hosting credentials, and documentation written so any competent engineer can pick it up cold. The source, the data, and the accounts are in your name.
Working software. Not slide decks, not status updates, not a promise about what is coming next sprint.
What happens when something breaks.
The answer most shops will not give you before you sign. There is no mandatory monthly fee to keep the lights on, because a support subscription is a smaller version of the thing you are leaving.
01
Walk away clean
Take the code and owe nothing. You hold the source, the accounts, and documentation good enough to hand to any other developer. Nothing stops working because you stopped paying us.
02
Or keep us on, hourly
Priced by the complexity of what we built and agreed in writing before handover, not invented the day something goes wrong.
03
Triaged by severity
Critical means the business cannot operate: picked up immediately, priced accordingly. A simple change goes into the next available week at the ordinary rate.
The full support and financing model, including why we publish the model instead of a rate, is on the pricing page.
The same six steps, entered through procurement.
The build process does not change for government work. What changes is the front door. Because we are already pre-qualified, a ministry or agency can move straight to a statement of work instead of running a full open competition, which is usually the slowest part of getting anything built.
Step one is often earlier than this page implies. If the question is whether an existing system should be extended or replaced, that gets answered by a fixed-price condition assessment first, and the six steps below only start if the answer turns out to be a build.
OAG-RFQ-26-068
Runs to 2030-07-07
Pre-qualified supplier to the Office of the Auditor General of British Columbia
Digital Services. Qualified in three categories: Public Cloud Services, Application and System Design, and AI Readiness and Adoption.
ON-003317-03
Pre-qualified, Province of British Columbia Multi-Use List, Service Area 3
Software Development and Testing. The provincial standing list ministries draw from when they scope a build.
BC Digital Marketplace
Registered supplier
Listed on the province’s marketplace for digital opportunities, so BC public bodies can find and invite us directly.
Delivery in progress
We hold an active contract with a Canadian provincial government ministry, client name withheld under contract confidentiality.
To be exact about what the first three are: a pre-qualification is permission to be invited, not a contract award and not a guarantee of work. It means the province has already reviewed us against its criteria and cleared us to bid, so a ministry can go straight to a statement of work instead of running a full open competition.
Four things we will not bend on.
Principle 01
Fixed price, never hourly
Hourly billing pays a shop to take longer. One quoted number, agreed before kickoff, pays it to ship the right thing. Scope changes are requoted in writing before any new work starts.
Principle 02
You own the outcome
Source code, data, hosting accounts, documentation. All of it in your name at handover. We do not build dependency into the delivery and call it a support plan.
Principle 03
You talk to whoever is building it
No account layer, no ticket queue between you and the code. When you ask why something works the way it does, the answer comes from the person who made that decision.
Principle 04
Lean by design
We stay small on purpose so overhead does not end up in your invoice, and we bid as prime and staff up on award rather than carrying a bench you would be paying for.
Free teardown. In writing. Zero obligation.
We go through your current systems, ask the pointed questions, and send back a written breakdown of what we would build and what it would cost. If the honest answer is that you should keep what you have, that is what the write-up will say.
Prefer to write it down first? Send the details by email and you get a reply from Eric, not an autoresponder.