The software between a phone call and a finished job

The best sign that a business needs custom software is a person doing something a computer should be doing. Retyping a form into a spreadsheet. Building the same report from scratch every week. Remembering to follow up. Sorting photographs into an order before any real work can start. Checking whether a customer has sent the document you asked for three days ago.

None of that is hard. It is just endless, and it is the first thing to break when the business gets busy. It is also exactly what software is good at.

We do not sell a platform and we are not resellers. Every project is written for one business, runs on that business's own domain and accounts, and belongs to that business at the end.

• Intake and quoting

  The front door of the business, working while you are on a job.

  A public request form that opens a file the moment it is submitted, acknowledges the customer immediately so they know it landed, works out what is needed for that kind of request, and tells you a new one has arrived.

  • Acknowledgement to the customer within seconds
  • A checklist built from the type of job, not a generic one
  • Text and email alerts to you when something new lands
  • Every request numbered and findable later

• Client portals

  One link that answers where are we with this.

  A private page for each customer showing what has been received, what is still outstanding, the messages between you, and the finished work when it is ready.

  • Sign in by a link emailed to them, no password to lose
  • Uploads that go straight to storage, including large photo sets
  • Documents completed against documents outstanding, at a glance
  • Replies to the system's emails land on the right file automatically

• Reports and documents

  The thing you actually sell, generated from the record.

  The finished PDF or web document your business delivers, produced from the data instead of assembled by hand, with the reasoning printed alongside the conclusion.

  • The conclusion has to follow from the figures, or the system stops
  • Internal notes stay internal and never print on a customer copy
  • House style and layout, consistent every time
  • Additional report types added later, quoted individually

• Internal tools and dashboards

  For when the spreadsheet has outgrown being a spreadsheet.

  Scheduling boards, job trackers, pipelines, consoles. Built around how your business talks about the work rather than how a software vendor decided to name it.

  • One screen that answers what is happening today
  • Drag, click or type, whichever suits the person using it
  • Works on a phone in a truck, not only on a desktop
  • Exports to a spreadsheet when someone needs one

• Text and email that fires itself

  Follow up that happens whether or not anyone remembers.

  Automatic confirmations, reminders, alerts and nudges before a promise to a customer is broken. Text messaging is set up correctly and legally, which is more involved than it looks.

  • A2P 10DLC carrier registration, which US networks now require of any business number that texts
  • Consent, STOP and HELP handled the way the carriers demand
  • Hourly sweeps that catch a job about to run past its promised time
  • Alerts to your phone the moment a request arrives

• Payments and invoicing

  Getting paid without chasing it by hand.

  Invoices sent from the system, payable by card or bank transfer through Stripe, with the payment itself triggering whatever comes next.

  • Card details go to Stripe directly and never touch your system
  • Paying can open the portal or release the report automatically
  • The Stripe account is yours, and the money goes to your bank
  • No card numbers stored anywhere, ever

Two different things get called AI, and mixing them up is how businesses buy something they did not want. Building with AI means agentic tools write the software. That is how every project here is made, and it is described in full on the how we build page. Having AI inside means the finished system calls an AI service while it runs, on your bill, on your data.

The second one is optional, and most projects do not need it. Where it earns its place, it is for reading unstructured things: pulling a VIN and an odometer reading out of a set of photographs, or extracting the relevant figures from an insurance document that arrives as a scan. That is work that used to require a person and now does not.

Where it does not belong is anywhere the answer has to be right and checkable. Money is arithmetic and stays arithmetic. Conclusions are drawn from the record by rules you can read, not by a model's opinion. If a system we build uses AI at runtime, you will be told before it is built, what it costs per use, and what happens when it is unavailable.

A written scope

Plain sentences describing what will exist when it is finished, approved by you before anything is built.

A fixed price

One number, agreed in advance. It changes only if you add something that was not on the list, and then only with your say so.

Your domain and your accounts

It goes live on a domain you own, with hosting, payment and messaging accounts in your name. Not ours.

Handover documentation

How it works, where everything lives, and what to do when you want to change something.

Thirty days of support

From the day it goes live. Anything broken or wrong gets fixed at no charge.

Additions, quoted individually

Another report type, another screen, another integration. Priced one at a time as you need them. There is no monthly fee and there never will be.

Said early, so nobody spends a week finding out.

• Mobile apps for the App Store or Google Play. What we build runs in a browser, including on a phone. If you genuinely need a native app, we will say so and you should hire someone else.
• Rescuing someone else's abandoned codebase. Taking over an unfamiliar system built by another team is slow, unpredictable, and cannot be quoted honestly at a fixed price.
• Staff augmentation, hourly body shopping, or joining your engineering team. We take whole projects, not seats.
• Anything requiring a certification we do not hold. There is no SOC 2 report, no ISO certificate and no HIPAA compliance program here. If your project must sit inside one of those, we are the wrong firm and will tell you on the first call.
• Marketing sites with a content management system as the main event. We build the software behind the business. A brochure site is a job for a designer and a template.