Scope
The software that never clears the bar.
Every company has a list of things that would obviously pay for themselves and will never be worth a six-figure project. That list is what lanes are for.
Internal tools
The spreadsheet that quietly runs a department.
You know the one. Forty tabs, six macros, maintained by one person who is now unofficially the system of record.
Scheduling and dispatch
Who’s going where, with what, and what happened when they got there.
Quoting and pricing
Rules that currently live in one person’s head and a protected worksheet.
Approvals and routing
The email chain that is technically your approval process.
Internal dashboards
The numbers someone rebuilds by hand every Monday morning.
Integration
Two systems that refuse to talk.
The job currently done by a person copying numbers between two screens, twice a day, with the occasional typo.
Accounting and stock systems
NetSuite, QuickBooks, Sage, and whatever the warehouse actually uses, kept in step.
Customer records
Getting the data in, keeping it tidy, and making it match what the invoices say.
Vendor and partner feeds
The nightly file that arrives in a format nobody chose.
The old system nobody will replace
Too risky to rip out, too stubborn to cooperate. We make it cooperate anyway.
Customer-facing
The things your customers keep asking for.
Requests that are entirely reasonable and never make it to the top of anyone’s list.
Status and order portals
So they stop calling to ask where it is.
Sign-up and intake
Forms that catch mistakes before the customer hits send, instead of after.
Things customers can do themselves
Price calculators, booking, paperwork that fills itself in.
Customer notifications
Automatic, accurate, and not from a personal inbox.
AI, actually applied
Wired into the workflow, not bolted on the side.
A chat window next to your software is not an AI strategy. The useful version disappears into work people already do.
Reading paperwork for you
Invoices, purchase orders, contracts and certificates, read and checked and filed where they needed to go.
Sorting the inbox
Enquiries, emails, and claims that find their way to the right desk on their own.
First drafts that know your business
Replies and summaries written with your policies, your history, and your words.
Decisions with a paper trail
Software that can show its working when someone asks why, and someone always asks.
Where we’re careful
Some things don’t belong in a lane.
Safety systems, medical devices, and card payments you’d have to get certified. Anything where a bad week means someone gets hurt or a regulator calls. We’ve worked in oil and gas and healthcare long enough to know where that line sits.
Genuine experiments sit outside a lane too. If nobody knows whether the software can be made to work at all, that is a research job rather than a building job, and we’ll say so. A lane is for building software, not for finding out whether the software could exist.
If you’re unsure which side of that line your project sits on, ask. Answering takes about two minutes.
Next step
Tell us three things you wish you could build.
We’ll tell you which one we’d build first, and roughly how long it would take. Twenty minutes, no slideshow.