How it works
Find it. Build it. Hand it over.
1
Find it
Real time in your week, not a workshop. We're after one sentence: "the thing in my way is ___." No sentence, no project, and we'll tell you that instead of selling you something.
2
Build it
We don't start from zero. Your build gets the parts that already work, with a screen or without one, and you pay for the part that's yours.
3
Hand it over
You own it. Some builds are a fee. Some are a fee plus a piece of what gets built, when we're building the thing alongside you. You'll know which on the first call, and it's written down.
Build it
One stack, kept running, shared by every build.
The expensive parts of business software are the same every time: signing people in, taking payments, scheduling, texting and emailing customers, reading documents, collecting signatures, keeping QuickBooks straight. We've built each one and we keep them running: the payment compliance and the carrier registration for texting. Because many businesses run on the same parts, the cost of each is shared across the businesses that run on it instead of carried by one, and nobody has to become the expert in all of them. Your build starts with them already working, and you pay for the part that's yours.
What you get
Software you use
A screen for the job: pricing it, signing it, working the list, approving the bill.
Software that just runs
No screen. It reads the documents, watches the source, screens the list, files what was signed, and tells you when it's done.
Screen or no screen is decided by the kind of work and what the people using it expect.
Before any code, a written description of what it will do, and a wireframe when there's a screen.
What it's built from (already ours)
- Sign-inA link in their email. No passwords to reset.
- PaymentsCards and deposits, taken on site.
- SchedulingOffers the customer three times from the nearest technician, a time you already agreed on, or the next one open. The customer picks one or asks for new options.
- Texts and emailReminders and updates, with the opt-out rules handled.
- Document readingPDFs and forms turned into rows a person checks before anything is billed.
- SignaturesSigned on site or by link. The PDF files itself.
- QuickBooks syncNothing typed twice. Estimates, invoices and payments land where the books live.
- Customer portalThey see where their job stands without calling you.
- Works with your AI assistantThe ChatGPT or Claude you already use can draft into the tool. A person still approves.
How it's built
- We find the real problem before anything is built. If what you asked for won't help, we say so.
- A person approves anything that bills, sends, or signs.
- The AI reports what is on file. It never invents a number to make things look better.
What we build on
Boring, proven, and already talking to each other.
We don't invent infrastructure. We pick tools that have been running other people's businesses for years, then wire them to yours. And because most of what we build touches customer data, data privacy, cybersecurity, and AI governance specialists are part of our extended team, not an afterthought.
- Hosting and data
- Vercel · Neon · Railway · GitHub
- Money
- Stripe · QuickBooks
- Messages and meetings
- Resend · Twilio · Gmail · Zoom
- Sales and outreach
- Apollo · Apify · Instantly · Dripify
- AI
- Claude · OpenAI
- Maps · Calendar · Workspace
- Privacy, security and AI
- Data privacy, cybersecurity, AI governance and data integrity specialists
- Built by us
- Custom APIs, and MCP servers that let AI assistants such as Claude use your tools directly.
- Yours
- Your CRM, or whatever else you already run: if it has an API, it goes on this list.
How we get paid
Some builds are a fee: you pay for the build and you own what gets built. Some are a fee plus a piece of what gets built, when we're building the thing itself alongside you. Which one applies is decided on the first call, and it's written down.
Who does the work
Our team runs discovery and runs the build. Discovery is a specific process: we identify the problem, then the outcome that would fix it. Everything we build is measured against those outcomes, from intake through prototype, testing and beta. Each build gets its own engineering lead. The extended team behind it covers engineering, design, marketing, data privacy and cybersecurity, AI governance, data integrity, and whatever specialty the build calls for. We staff to the shape of the build rather than making the build fit a fixed team, which is how a capture-planning tool for engineering firms and a plain-language estimate tool for a one-man RV shop come out of the same shop.
Questions about the money
- Who owns what gets built?
- On a fee build, you own what gets built. If we keep a piece, it's written down before we start.
- How do you get paid?
- Some builds are a fee. Some are a fee plus a piece of what gets built, when we're building the thing alongside you. Which one applies is decided on the first call, and it's written down.
- Can a small business afford custom software?
- Often, yes. That's what the code library is for: the parts every business needs are already built, so a small business pays for the part that's specific to it.
When we'd tell you not to hire us
- If the problem is the product, not the process around it.
- If you want someone to run your tool forever. We build it and hand it over.
- If we can't get to the one sentence.
