One fixed number.
Then you own it.
We build custom software for BC and Canadian organizations and hand over the source code. Builds start at $10,000 and scale with scope. Every one is quoted as a single fixed number, agreed before any code is written. No timesheet billing. No subscription. No retainer you forget to cancel.
- $10K to $1M
- Build range by scope
- $0
- Subscription fees
- 2 yr
- Financing option
- 100%
- Code and IP to you
Six things decide where your quote lands.
A single automation that removes a recurring manual job sits at the bottom of the range. A system that replaces four subscriptions and runs your operation sits in the middle. Multi-department and enterprise work goes to the top. These are the variables that decide which one you are.
Factor 01
How many people touch it
A tool for three dispatchers is a different build than one for sixty field staff across four roles with different permissions.
Factor 02
How many systems it talks to
Every integration is real work. Accounting, payments, payroll, mapping, a supplier feed. One or two is routine. Eight is a project of its own.
Factor 03
What has to come across
Moving ten years of records out of a tool that does not want to let go of them costs more than starting clean. We look at the export before we quote.
Factor 04
What it has to comply with
Public bodies and regulated work carry accessibility, records, and residency requirements. We build to WCAG 2.1 AA as standard, and the rest is scoped explicitly.
Factor 05
What happens when it is down
A reporting dashboard and a system your crews cannot dispatch without are priced differently, because they are engineered differently.
Factor 06
How settled the process is
If you can describe how the work runs today, we can build it. If it is still being invented, we scope a smaller first piece rather than quote a guess.
Three ways to fund the same build.
The engineering does not change. Only the way the cost is carried does.
Option 01
Buy it outright
Milestone billed, fixed quote
One number agreed before kickoff, billed against milestones you sign off as they land. Nothing is due for work that has not shipped. At final payment the code, the data, and the accounts are in your name.
- Fixed quote, not a range and not an estimate
- Scope changes requoted in writing, in advance
- Full source and IP transfer at handover
- Zero equity, zero ongoing obligation
Option 02
Finance it over two years
Then the payments stop
We size the monthly payment to roughly match what you already spend on the subscriptions the build replaces. Your software cost stays flat for two years instead of climbing. Then it goes to zero, and you own the thing.
- Monthly cost roughly matches today's SaaS bill
- Two-year term, then ownership transfers
- No renewal, no price increase at the end of it
- Same build, same handover, same documentation
Option 03
Trade equity for cash
Selective. Not for startups.
For established brick-and-mortar operations digitizing how they run. The cash fee comes down and we take a minority position instead, negotiated per deal. We do not publish a percentage because there is no standard one.
- Reduced cash, minority equity position
- Real diligence on both sides before anyone signs
- An honest no, in writing, when we pass
- Long-term relationship, not a one-off invoice
A narrower build-for-equity route exists for a small number of situations where there is no cash at all. It is heavily filtered and most applications are declined. If that is you, read No Capital? No Problem before booking anything.
There is no monthly retainer.
A support subscription is just a smaller version of the thing you are trying to get out of. So we do not sell one. Here is the whole model.
Path A
Take the code and owe us nothing
You have the source, the accounts, and the documentation. Run it in house, hand it to your own developer, or hire anyone you like. This is a genuine option, not a line we put here to look confident. If you never call us again, the system keeps running.
Path B
Keep us on, hourly, triaged by severity
An hourly relationship, with the rate set by the complexity of what we built for you and agreed in writing before handover, not invented after something breaks. Work is triaged:
- Critical. The business cannot operate.
- Now, priced higher
- Degraded. It works, but badly.
- Same week
- Simple change or new feature.
- Next available week
We publish the model rather than a rate, because a rate quoted before we know what we are supporting is a number neither of us should trust.
Fifteen minutes of your team's time.
The real reason businesses stay on software they dislike is not price. It is the fear of the switch. So we take that side of it.
Nobody on your team should spend more than about fifteen minutes getting set up: a new login, a new password, and back to work. We move the data, we check it against the old system, and we plan the cutover around your calendar rather than ours.
See the full sequence on how a build actually runs.
The number on the proposal is the number you pay. If we got the estimate wrong, that is our problem, not your next invoice.
Check that we are a real company first.
Every figure below is a bound policy or a registry number you can look up without asking us for anything.
- Commercial general liability
- $5,000,000
- Professional liability (E&O)
- $2,000,000
- Cyber liability
- $2,000,000
- WorkSafeBC account
- 201966367
Bound and in force.
Bound and in force.
Bound and in force.
Active. Clearance letter on request.
- Federal corporation (CBCA)
- 1730441-2
- BC extraprovincial registration
- A0142791
- Business number
- 771523834 RC0001
- Ownership
- Canadian
BlueStone AI Inc., incorporated 2025-09-09.
Registered to carry on business in British Columbia.
Canada Revenue Agency.
Canadian-owned small business.
Certificates of insurance and a WorkSafeBC clearance letter are issued on request, usually the same day. BlueStone AI Inc. is a small supplier under the Canada Revenue Agency threshold and is not currently registered for GST/HST, so invoices carry no GST line.
Why do you not publish a price list?
Because a price list for custom software is either fiction or a bait number. What we do publish is the floor, $10,000, the six things that move a quote above it, and the fact that every engagement is quoted as one fixed number before any code is written. You get your number after a free 30-minute teardown, in writing.
Why fixed price instead of hourly?
Hourly billing pays the builder to take longer. Fixed price pays the builder to ship the right thing. We do the scoping work up front, which is why every engagement starts with a free teardown, and then the number on the proposal is the number you pay. If we underestimated, that is our problem. If you change the scope, we requote the difference in writing before any new work starts.
What does support cost after handover?
There is no flat monthly retainer. You can take the code and owe nothing, which is a real option and not a threat. If you want us on call, it is an hourly relationship, priced by the complexity of what we built and agreed in writing before handover. Work is triaged by severity: something critical gets picked up immediately and is billed accordingly, and a simple change goes into the next available week at the ordinary rate.
Can I pay for it monthly instead of up front?
Yes. We can structure the build so the monthly payment roughly matches what you already spend on the subscriptions it replaces, spread over two years. Your software cost does not go up while you are paying it off. At the end of the two years you own it outright and the payments stop.
How disruptive is the switch for my team?
Nobody on your side should spend more than about fifteen minutes getting set up: a new login, a new password, and back to work. We move the data. Cutover is planned around your calendar, not ours.
Do you take equity instead of cash?
Sometimes, and selectively. It is for established brick-and-mortar operations digitizing how they run, not for startups. The structure is a reduced cash fee plus a minority equity position, negotiated per deal. We do not publish percentages because there is no standard one.
What happens if we stop working together?
Nothing breaks. You already hold the source code, the data, and the hosting accounts, and the documentation is written so another engineer can pick it up cold. That is the difference between owning software and renting it. Leaving is a decision, not an extraction project.
Get your actual number.
Book a teardown. We go through how your business runs and what you currently pay for, and you get a written breakdown back: what we would build, the fixed quote, the timeline, and which of your existing tools we think you should keep.