Custom apps & internal tools.
Somewhere in your business there's a spreadsheet doing a job software should be doing. One person understands it, nobody is allowed to touch the formulas, and the whole shop quietly routes around it. It works — until the week it doesn't.
We build the tools those spreadsheets stand in for. Booking systems that fill the calendar without a phone call. Quoting tools that turn a site visit into a number the same day. Client portals, scheduling boards, the screen your crew opens every morning — built around how your business actually runs, not how a software vendor guessed it might.
Where it sits in the engine.
An app usually lives at the third component — a clear way to say yes — or just behind it. Booking, quoting, paying: each of those is the yes itself, made easier to give. The scheduling board and the client portal sit behind it — the machinery that keeps a yes from leaking away between the signed quote and the finished job.
The fourth component still applies. A tool that runs your operation produces numbers the spreadsheet never could — jobs quoted, jobs won, time to done — which is a way to see what's working, built into the way you work.
The four components are laid out in what we build.
What's included.
Scoping and a written spec
We watch how the work actually moves through your shop, then write down what the tool does — and doesn't — before anything gets built. The spec is yours either way.
Design in Figma
Every screen designed before it's coded, for the person who'll use it forty times a day — not for a demo.
The build
Custom tools in React, running on Google Cloud. When your business already lives in Microsoft 365 and needs something fast, Power Apps puts a working tool inside the software you have.
Integrations
Connected to what you already run — calendar, accounting, CRM, email — so the tool joins the shop instead of adding one more place to retype things.
Accounts and permissions
Logins and roles where they're needed: the office sees everything, the crew sees today's jobs, the client sees their own.
Deployment and hosting setup
Set up in your accounts, under your name, with backups — and running costs visible to you from day one.
Walkthrough and handoff docs
Your team trained on the tool, and documentation written for whoever joins after them.
When you shouldn't build.
Custom software is the expensive way to solve a problem, and sometimes the wrong one. If an off-the-shelf product does what you need for forty dollars a month, we'll tell you so in the scoping call and point you to it. That's a cheap meeting for you and a short one for us.
Custom earns its cost when the process is the business — when how you quote, schedule, or keep customers informed is part of why they pick you. Bending that process to fit someone else's software costs more over the years than building a tool that fits. The spec is where we make that case with numbers, or concede it.
What it costs.
This work is quoted per project. Three dials shape the number — quality, speed, and size. You tell us where each one sits; we tell you what fits. The full picture is in how we price.
If what you need is the whole path — found, landing, saying yes, measured — that's your first Customer Engine, one engagement starting at $10,000.
Questions we hear.
Who owns the code?
You do. The code, the design files, the cloud project, the accounts it all runs in — delivered in your name at handoff. If we disappeared tomorrow, any competent developer could pick it up from the docs.
What does it cost to run after launch?
Running costs go in the spec, before you commit to the build. As a shape: a small React tool on Google Cloud tends to cost tens of dollars a month in hosting at small-business scale, and Power Apps rides on Microsoft 365 licensing you may already pay for. Billing is set up in your accounts, so the number is one you see — not one you take our word for.
What about maintenance?
We build on stable, widely used technology so the tool doesn't need constant tending. Changes — a new field, a new report, a new screen — are quoted like any other work, or covered by a monthly arrangement if you want them regularly. Either way, the handoff docs mean the tool isn't tied to us.
How long does a typical tool take?
A focused internal tool — one job, a handful of screens — usually lands in a matter of weeks. A portal with accounts, permissions, and integrations runs a few months. Anything more precise than that before scoping would be a guess; the spec comes with a real schedule, and we hold to it.
Let's talk.
A short, three-step form. We reply within two business days. Your first Customer Engine starts at $10,000; everything else is quoted per project.