Founders accountable, senior team building
The founders stay accountable on every Pilot and you deal with senior members throughout. No agency stack. Capacity is honest, which is why the monthly cap is set by what we can deliver well.
The 30-Day Pilot Build
$5,000 launch rate. Senior team, founders accountable. Completion guarantee and on-time guarantee. The Pilot is a real delivery, not a diagnostic.
20 minutes on the fit call. Or two minutes on the scorecard first. Your choice.
Pilot pricing
USD 5,000
Launch rate. The only price. Acceptance-gated delivery.
Five working modules, two standard and three custom
Authentication and role-based access control
Production-ready deployment
Completion and on-time guarantees in the contract
Pilot graduates carry a twenty-five percent discount off the first milestone of their BuildXLR8 engagement.
What You Actually Get
Eight deliverables in the contract. Nothing in the room that is not on this list. Nothing on this list that we do not hand over per the agreed contract.
User authentication and role-based access control are standard. Three custom modules are built around the highest friction parts of your operation. All five named in the written quote before we start.
A one-page scope doc, the five modules, the acceptance checklist. The contract you sign, not a pitch deck.
Shipped to AWS or Cloudflare. The deployment is handed over per the agreed contract. Hosting, if you want us to run it, is billed separately under WebXLR8.
Login, roles, permissions, password reset, invite flow. The two standard modules that make software safe to hand to the team.
The codebase is handed over with documentation, demo videos, and training, per the agreed contract. Your team can onboard itself.
Direct access to the team on WhatsApp and email during the first thirty days of live use. Bugs fixed, tweaks applied, not an upsell.
The codebase is handed over, with documentation, demo videos, and training, per the agreed contract. We are not the only ones who can run it.
Completion guarantee: nothing deploys until a signed acceptance checklist passes. On-time guarantee: if a slip past a two-week grace is our sole fault, ten percent off per week late, capped at fifty percent.
We do not charge you separately for deployment, docs, or handover. If the scope needs to grow beyond five modules, it becomes the first chunk of a larger engagement we quote after you have the first outcome in your hands.
What We Need From You
Custom software projects fail when clients have to run them. The Pilot is designed around your existing operation, not your calendar. Here is the total ask.
Spread across two weeks of kickoff. One discovery session, one check-in, one review. We handle the rest.
The spreadsheet, the WhatsApp history, the old app. We shadow and build. No forms to fill, no transformation memos to read.
Someone empowered to say yes or no in 24 hours. We will not ping five stakeholders for one scope question.
Promise
Three questions. One yes is enough. The Pilot was scoped for exactly the operator who answers honestly here.
Is your ops still running on Excel?
Is WhatsApp or email your system of record?
Is the senior person in your team the bottleneck when they are unavailable?
Proof
Three facts. No fabricated metrics. No 3x, 5x, 10x claims. Real credentials, real delivery.
The founders stay accountable on every Pilot and you deal with senior members throughout. No agency stack. Capacity is honest, which is why the monthly cap is set by what we can deliver well.
We do not claim 3x, 5x, or any other percentage we cannot back. When the first Pilots deliver, the numbers will come from the clients who opt in to share them.
Every build is delivered by senior engineers. Our sibling brand WebXLR8, under the same parent company, adds hosting and delivery depth.
Plan
On a free fit call and a short follow-up, we map the workflow that is breaking and confirm the Pilot shape is right, or say it is not.
We send a written quote naming all five modules and the acceptance checklist. Nothing deploys until that signed checklist passes. Scope locked, $5,000.
A senior team builds across the 30 days with weekly check-ins. On sign-off, the codebase is handed over with documentation, demo videos, and training, per the agreed contract.
Five Modules, In Practice
Every Pilot starts with two standard modules: user authentication and role-based access control. The three custom modules below are examples for the verticals we build into. Yours will be scoped on the fit call.
The Production Schedule Board
A shared board replacing the planning spreadsheet, with job state, machine assignment, and run history.
The Quality Check Capture
Inspection entries with timestamps, photos, and pass or fail logic. The paper QC sheet retired.
The Inventory Count Sync
Stock in and out captured at the point it happens, so the count is current instead of reconciled at month end.
Plus the two standard modules: authentication and role-based access control.
The Dispatch Board
A shared board replacing the WhatsApp thread, with state (pending, assigned, on route, delivered) and per-vehicle history.
The Driver Log Capture
Pre-trip, on-trip, post-trip entries with timestamps and photos. No more paper logs.
The Customer Status Link
A read-only link your customer can open to see where their load is without calling dispatch.
Plus the two standard modules: authentication and role-based access control.
The Order Intake Form
One form for sales reps replacing the master sheet, with stock validation at entry.
The Approval Router
Orders above a threshold route to the senior person with one-click approve or reject.
The Shipment Tracker
Internal view of what has shipped, what is stuck, and what is coming back as returns.
Plus the two standard modules: authentication and role-based access control.
The Shipment Tracker
Every consignment from purchase order to clearance to delivery, with status the whole team can see.
The Document Vault
Invoices, packing lists, bills of lading, and certificates filed against the right shipment, found in seconds.
The Landed Cost Calculator
Duties, freight, and charges rolled into a true per-unit cost instead of a spreadsheet guess.
Plus the two standard modules: authentication and role-based access control.
Two Months After the Pilot
The Pilot replaces five workflows. The knock-on effect is bigger. This is what operators who close their own Spreadsheet Tax report six to eight weeks in.
Because the software, not their memory, is the source of truth. The team operates without them in the loop.
Onboarding is the software, not a tribal-knowledge transfer over three months.
Not off whichever copy of the spreadsheet someone forgot to refresh.
The bottleneck is not a person anymore. Growth does not double the reconciliation tax.
Completion and On-Time Guarantees
The guarantees are in the contract, not the marketing copy. Both halves written in plain language.
Nothing deploys until a signed acceptance checklist passes. We keep working until it does. This is a completion guarantee, not a cash refund.
Signed acceptance checklist
Written into the scope upfront. You sign it off before anything goes live.
We finish what we scoped
If the checklist does not pass, we keep building at no extra charge until it does.
No cash refund
The guarantee is completion, not a refund. The Pilot ships, or we are still building.
If a slip past a two-week grace is our sole fault, ten percent off per week late, capped at fifty percent. The clock is on us, not on you.
Two-week grace
The penalty starts only after a two-week grace beyond the target date.
Our sole fault
Triggers only when the slip is ours, not when the scope or your inputs shift the date.
10% per week, capped at 50%
Credited against the fee. The cap is fifty percent.
Honest Exclusion
If You Do Nothing
Each month you defer, the cost grows. Not in invoices. In the hours you cannot get back, the hires who never close the gap, and the senior person who stays the bottleneck.
Month 1
Early signs
~20 hrs
Lost this month to reconciliation
The same workflow keeps breaking. The team adapts to the friction instead of fixing it. You normalise the loss because it never lands on an invoice.
Month 3
Compounding
1 hire
Burned. Problem unchanged.
You hired someone to "handle the spreadsheet." Three months in they own the same problem. The senior person still touches every case. Hiring budget gone, pain unchanged.
Month 6
Compounded loss
180 days
Lost. Two Pilots could have shipped.
Six months of workarounds compounded. One senior hire further from solving it. The Pilot would have shipped twice by now, and BuildXLR8 cycle one would already be in flight.
The bounded way out
The Pilot is the only path on this page that ends with working software in your team's hands. Twenty minutes on the fit call is the next step.
After your Pilot, BuildXLR8 picks up where it stopped.
FAQ
Anything not on this list? Book a fit call and we will work through it together.
Most clients who finish a Pilot continue with BuildXLR8, our full custom operational software build. BuildXLR8 picks up where the Pilot stopped: more modules, integrations, the full operating system, built in 30-day milestone cycles. Pilot graduates carry a twenty-five percent discount off the first milestone of their BuildXLR8 engagement (the first milestone only, not the entire engagement).
Yes. For clients ready to commit, BuildXLR8 is scoped from the first call with cycle one structured to do the de-risking the Pilot would have done. The Pilot is the cheapest first yes, not the only door.
We will flag it on the fit call. The Pilot is intentionally bounded at five modules so delivery is predictable. If you need more, BuildXLR8 is the path: 30-day milestone cycles, scoped per build, with a four-part guarantee stack. Pilot graduates get twenty-five percent off the first milestone of their BuildXLR8 engagement (the first milestone only, not the entire engagement).
Two are standard on every Pilot: user authentication and role-based access control, the plumbing that makes software safe to hand to a team. The other three are custom, built around the highest friction workflows in your operation. We name all five in the written quote before we start.
Modern defaults with deliberate choices. Node.js, React or Next.js on the front end, PostgreSQL for data, AWS or Cloudflare for hosting, and integrations with whatever your team already uses (WhatsApp Business, Google Workspace, Microsoft 365). The stack is picked for your situation, not our preference.
Yes. Many Pilots lead to follow-on engagements where additional modules, integrations, and automations layer onto the foundation we built in the first 30 days. We do not charge a separate onboarding for you to continue with us.
By default we deploy to a production-ready Cloudflare or AWS environment under your account. You hold the deployment. If you prefer us to host and manage it, hosting is billed separately under our sibling brand WebXLR8.
Where the workflow warrants it, yes. We can build the Pilot with right-to-left Arabic support and mixed-language content. Flag it on the fit call so we can scope it correctly.
The first thirty days of live use are covered as hypercare, part of the Pilot. After that, the platform can enter BuildXLR8 Assurance, our care plan that maintains it. Hourly ad hoc support is also available for clients who prefer not to subscribe. You are never locked in.
A dynamic monthly cap, set by current delivery capacity. The founders stay accountable on every Pilot and a senior team builds. If the cap for the month is reached, we add you to a waitlist and quote the next available start. Our outreach never pauses, so the waitlist is how we keep delivery honest.
Not Ready for a Call Yet?
One line describing the workflow that is costing you the most. We will reply within one business day with either a fit call invite or an honest "not a fit" note.