Custom applications
A small web application built for one job when no product fits it, running on your own data with a login for the people who need it.
Capability 02 / 05 · Development & integrations
Stop retyping the same information.
We write the code between the software you already pay for, and we build the small applications there is no product for. A job is entered once and appears everywhere it belongs, including the spreadsheet the office actually runs on.
Fixed-scope installations · Monthly service plans · A reply within one business day
01 / 04 What’s included
Six things included. Nothing you will not use.
Work is scoped to the systems you already run. We do not replace software that is working.
Field software integration
ServiceTitan, Housecall Pro, Jobber, and the rest, connected through their APIs so jobs, customers, and statuses move without a person in the middle.
Accounting integration
QuickBooks wired to the field software so invoices, payments, and customer records match without a monthly reconciliation night.
APIs and data pipelines
Scheduled jobs that pull, clean, and file data between systems, with retries and a log you can read when something fails.
Reporting
One brief each morning with today’s jobs, yesterday’s missed calls, open quotes, and revenue received, pulled from the software you already use.
Document automation
Forms, packets, and filings generated from the source document instead of retyped, in the exact layout you already send.
02 / 04 How it works
Four steps, in the same order every time.
Integrations fail in the gaps between systems, so we map the gaps before writing anything.
Step 01 / 04
Trace
We follow one real job from the first call to the paid invoice and write down every place a human retypes something or a system loses it.
One job, tracedHandoff map
Step 02 / 04
Specify
We write what will move, in which direction, on what trigger, and what happens when the other end is down. You approve that document before any code exists.
Data contractSigned before code
What movesJob, customer, status
DirectionOne way
TriggerOn job close
If the other end is downQueue and retry
Approved by youBefore any code
The scope is this document
Step 03 / 04
Build
We build against a copy, with tests on the parts that move money, and keep your live system untouched until it passes.
Build conditionsYour live system untouched
Built against a copy of your data
Tests on every path that moves money
No writes to the live system
Passes, then cuts over
Nothing touches production until it passes
Step 04 / 04
Cut over
We switch it on during a quiet window, watch the first day of real traffic, and keep the old path available until the new one has run clean.
CutoverRollback ready
Switched onQuiet window
First day of real trafficWatched
Old pathStill available
RetiredOnly after a clean run
You are never left without a way back
03 / 04 Proof
Working software, not a slide.
One internal build that evidences this capability. It runs today. No client results are claimed.
Internal build
Shipping document automation
Every export shipment meant retyping a supplier’s pack list into a filing, a carrier email, and a spreadsheet, with the transcription errors that implies.
- Watches a folder and routes dropped PDFs to the right customer rules automatically
- Generates the filing, the email body, and the export master from one extraction
- Shows a “not configured” badge instead of faking a send when carrier credentials are absent
Python · FastAPI · SQLAlchemy async + aiosqlite · Jinja2 + HTMX · openpyxl · watchfiles · Docker
See the build04 / 04 Who it’s for
If this is your week.
Three situations we are called about most. If none of them are yours, the assessment is still free.
The same customer address gets typed into three systems before the truck leaves the yard.
Nobody trusts any of the three, so the office keeps a fourth copy in a spreadsheet. You need one place that feeds the others.
Somebody spends the last Friday of the month reconciling the field software against the books.
The totals never match and the difference is always a handful of jobs that were closed in one place and not the other.
There is a report you want every morning and no software that produces it.
You have been told it needs a different platform. It usually needs about two hundred lines of code against the platform you already have.
Questions
What we are asked first.
Do I have to change the software we use?
No, and we will argue against it. Replacing field software costs a season of retraining. We build against what you already pay for, and we say plainly when a setting in that software does the job and no build is needed.
What if the software has no API?
Then we tell you that before the proposal, not after. Some systems only allow scheduled exports, which is workable but slower. Some allow nothing, and in that case the honest answer is that the integration is not possible at a sane price.
Who owns the code?
You do, for anything built for you. It is delivered as readable source with a written description of what it does and where it runs, so another engineer can pick it up without calling us.
What happens when one of the systems changes an API?
That is what the monthly service plan covers: we monitor the connections, fix them when a vendor changes something, and tell you in the weekly summary. Without a plan, it becomes a fixed-scope repair.
Start here
Bring us one job that takes too long.
The assessment follows a single real job from first call to paid invoice. The one-page summary names where the time goes and what it would cost to remove it.
Received.
A reply within one business day, from the studio that would build the system. If nothing arrives, call or text (616) 227-4477.