The front door
Five working modules of your operation, live in 30 days.
Not a prototype, not a proof of concept, and not a slide deck. Deployed software your team logs into, replacing the spreadsheet and the WhatsApp group it grew out of. You own the code.
- Building since 2021
- Around 100 clients
- Founder led
The Signed Checklist Guarantee
Nothing deploys until every item on the checklist we both signed passes.
Before you pay anything, we write the acceptance criteria together: a plain, signed, pass or fail list of what the software has to actually do. If the build does not clear that list, we keep building on our own money until it does.
There is no cash refund, and we will tell you why rather than bury it. A half-built system is worth nothing to you, so handing your money back would leave you exactly where you started, thirty days older. Finishing it is the only outcome worth guaranteeing. You go live, and release the balance, once it works the way we agreed in writing.
The On-Time Terms
The Pilot is built in 30 days.
Miss that date for reasons that are solely our fault, past a two week grace, and we discount 10% for every further week late, capped at 50%.
It covers delays on our side only, not a missed access handover, an absent approver, or a feedback window that went unanswered. Scopes containing a third-party integration carry no timeline commitment, because a third party review cycle is not ours to control.
What ships
Everything in the contract, and nothing that is not.
5 working modules, deployed
Two standard on every build, user authentication and role based access control. Three custom to the workflows costing you the most right now.
A single screen dashboard
Desktop and mobile. The whole operation on one screen, so the answer to "how are we doing" stops being a phone call.
An automatic end of day summary
Pushed to you. What was produced, what shipped, what got flagged. Without anyone assembling it.
The codebase, in your systems
With documentation, demo videos, and training, per the contract. Not held in our account pending anything.
Before any money moves
You see it before you buy it.
Map and Scope happen at no charge once a twenty minute fit call confirms the problem is worth solving with custom software. If the fit is not there, we say so on the call and point you somewhere useful.
A wireframe of your operation, running clean
Your own workflow, on screen, before you have paid anything. This is the part most people have never seen before they commit budget.
A signed acceptance checklist
A plain, pass or fail list of what the software must actually do. Sent as its own document with the proposal. Nothing deploys until every line on it passes.
Map. Lock. Build. Own.
One process. You learn it once, then watch it repeat.
The Pilot is one full turn of this loop. BuildXLR8 is the same loop, once per 30-day milestone. That is the whole method.
01
Map
We watch how the business actually runs today.
The Excel files, the WhatsApp groups, the paper, and the workarounds nobody mentions in meetings. It comes back as a one-page picture of your operation. Most owners tell us it is the first time they have seen the whole thing on one sheet.
02
Lock
We fix what gets built, and what it costs, in writing, before anyone codes.
You get a wireframe of your operation running clean, and an acceptance checklist we both sign: a plain pass or fail list of what the software has to do. Both happen before you pay anything.
03
Build
A senior team builds it. A working module goes live, not a slide.
You see running software rather than a status report. The same people who scoped it write it, so nothing is lost in a handover that never happened.
04
Own
The code lands in your systems, with documentation and training.
Not held in our account pending final payment, and not licensed back to you. Yours, per the contract, with the demo videos and training to go with it.
Example scopes
The three custom modules, by sector.
Authentication and role based access are on top of these, on every build. Your three get chosen during Map, against what is actually costing you.
Manufacturing
- Work order assignment, with production tasks pushed to the floor from one screen
- Inventory in and out, with timestamps and the user who moved it
- Production status and end-of-day reconciliation, flagging what does not add up
Logistics
- Job assignment and dispatch, run from one screen instead of a group chat
- Driver and field status updates from a phone, marking pickup, delivery, and delay
- A live status view of every active job on one dashboard
Professional Services
- Job and engagement tracking, from intake through delivery
- Time and cost capture attached to the work rather than reconstructed later
- A billing readiness view showing what is deliverable and not yet invoiced
Scope discipline
What the Pilot does not include.
Holding the scope is the only reason 30 days is a real number rather than an optimistic one. These are out, and saying so now is cheaper for both of us than discovering it in week three.
- Real time GPS tracking, ELD integration, or hardware installs
- IoT and sensor integration
- Enterprise compliance frameworks
- More than the agreed five modules
- Ongoing maintenance, which is Assurance and is quoted separately
Integrations are possible where a public API exists, for example Tally Cloud or QuickBooks. They are timed and priced separately, and a scope containing one carries no timeline commitment, because a third party review cycle is not ours to control.
FAQ
Questions people ask before they commit
What exactly do I get for USD 5,000?
5 working modules, deployed and live, in 30 days. Two are standard on every build: user authentication and role based access control. Three are custom to the workflows costing you the most right now. Plus a single screen dashboard, an automatic end of day summary, and the codebase handed to your systems with documentation and training.
What happens if it is not finished in 30 days?
Miss that date for reasons that are solely our fault, past a two week grace, and we discount 10% for every further week late, capped at 50%. It covers delays on our side only, not a missed access handover, an absent approver, or a feedback window that went unanswered. Scopes containing a third-party integration carry no timeline commitment, because a third party review cycle is not ours to control.
What if I do not like what you build?
Nothing deploys until every item on the checklist we both signed passes. We write those criteria together, before you pay, as a plain pass or fail list. If the build does not clear it, we keep working until it does. There is no cash refund, and we will tell you why rather than bury it. A half-built system is worth nothing to you, so handing your money back would leave you exactly where you started, thirty days older. Finishing it is the only outcome worth guaranteeing. You go live, and release the balance, once it works the way we agreed in writing.
I hired a developer before and got burned. Why is this different?
Because the two things that usually go wrong are removed before you pay. You see a wireframe of your own operation running clean before any money changes hands, and the acceptance criteria are signed in advance so "done" is not a matter of opinion at the end. You also hold the code the moment it ships, not at some future handover that never gets scheduled.
Do you have a version of this in my currency?
USD 5,000 is the price everywhere. One number, every market, published openly. It is the current launch rate. one price, every market. reviewed after three months.
How do payments work?
50% at kickoff, 50% on written acceptance of the working demo. Go live and the codebase handover happen once the balance clears.
What is not included?
Real time GPS tracking, ELD integration, hardware installs, IoT and sensor work, and enterprise compliance frameworks. More than the agreed five modules is also out, because holding the scope is the only reason 30 days is achievable. Ongoing maintenance is Assurance and is quoted separately.
What do you need from me?
One named person who can make decisions, with a day or two turnaround on questions, and access to the systems we are replacing or connecting to. That is genuinely it. The pace of the build tracks the pace of your answers.
Tell us what is breaking
We reply within one business day. If a The 30-Day Pilot Build is not the right call for you, we will say so and point you somewhere useful.
The full build
Put the whole operation on one system you own.
Your whole operation on one system you own, built in 30-day milestone cycles. Priced and approved one milestone at a time, and you can stop after any of them with everything already in your systems.
We keep two Pilot builds in delivery at a time.