A client portal that is the product
Sixteen working screens on day one: visibility, reputation, conversion, and the monthly receipt. We did not buy a dashboard and skin it. Every screen is ours, which is why we can add yours.
Walk through the portalBUILD
Some businesses do not have a marketing problem. They have an operation held together by spreadsheets, group texts, and one person's memory, and no amount of ranking fixes that. This is the lane for that work: a portal, a CRM, the internal tool nobody sells, the website. We build it on the platform we already run.
There is a version of your business that only exists in your head and in a spreadsheet somebody named final_v3. Everyone works around it. It costs you an hour a day and a job a month, and it has never been worth stopping to fix.
WHAT WE BUILD
This is not a portfolio of client logos. It is the software this company runs on, and it is the reason a build here is faster and cheaper than an agency starting from an empty folder. The parts already exist. Your build is the part that does not.
Sixteen working screens on day one: visibility, reputation, conversion, and the monthly receipt. We did not buy a dashboard and skin it. Every screen is ours, which is why we can add yours.
Walk through the portalThe job closes, the customer gets your tech's card on their phone, and the card is what asks for the review. Everything that lands comes back to one screen where you reply. We never buy, fake, or incentivize a review, and we will tell a client that out loud.
A grid of points dropped across a service area, each one asking Google where you land as if a customer were standing right there. Green where you rank, red where you do not. We built the measurement, the storage, the scheduling, and the map.
An assistant that can read a client's own data and propose real changes, with an approval step in front of anything that writes and an action log behind it. Custom AI that does work is a different thing from a chat box bolted onto a sidebar.
A card per person on the crew, a landing page behind it, an NFC chip and a QR that both resolve through links we can repoint later, and print ready artwork generated at real trim and bleed. The whole chain, because half a chain is a coaster.
Calls, forms, QR scans, and ad leads landing in one tagged inbox that exports clean. It reports the source we can honestly attach and does not claim attribution the data will not support.
One client runs their own estimating software. When a job closes there, it posts into their TVI account and the review flow picks it up, with the tenant taken from the key rather than the request body. We build the integration and the embed, so your team keeps working where they already work.
Built on the platform, handed to you, no page builder subscription and no rented template. If you already have a developer, we will hand them a punch list instead and get out of the way.
Most run three to four months. You see working software at the end of every phase, not a status deck. If a phase does not land, you find out from us before you find out from your team.
Not a questionnaire. We watch the job go from the phone ringing to the invoice clearing, we write down every place the work leaves software and lives in someone's head, and we come back with a scope and a number. If the honest answer is that you do not need this, that is what the discovery says.
What you seeA written scope, a phase plan, and a fixed number before you commit to anything past discovery.
Customers, jobs, locations, and whoever touches them, imported and reconciled. This is the unglamorous phase and it is the one that decides whether the rest works. Everything after it is built on top of a set of records you trust.
What you seeYour real data in your own portal, on a real login, with the import you can re-run.
The CRM, the job board, the quoting flow, the internal screen nobody sells. Built against your data from phase one, shaped around how your team already works rather than how a software company wishes they did.
What you seeWeekly builds you can click, in your account, and a standing call where you break them in front of us.
Follow up that fires on its own, the handoffs that used to be a text message, and the reporting that answers the question you actually ask on Monday. Then we train the people who have to live in it, which is the step most builds skip and then blame the client for.
What you seeThe automations running on live jobs, and your team using the thing without asking you how.
Your data, exportable, in a format that opens somewhere else. Your accounts in your name. Documentation written for the person who has to run it after you. Ongoing maintenance and hosting are available where a build needs them, and they are optional, not a lock.
What you seeAn export, the keys, the docs, and a maintenance quote you are free to decline.
This is the part worth reading twice, because it is where most build shops are quiet. Every line here is the same commitment we already make on the retainer side.
Starting points
Starting points, not a checkout. A build is scoped on a call and priced in discovery, and the number does not move after that unless you change the scope. Ongoing systems work is quoted monthly on top, and only where a build needs it.
These are the same figures on the rate card. Discovery is where the real number comes from, and you get it in writing before phase one starts.
The full rate cardWe were the customer before we were the vendor.
Brayden started Dunn Restoration, exited a pest control company, and founded lighting companies before any of this existed. Service businesses and brick and mortar. Trucks, crews, a phone that has to get answered on a Saturday, and payroll that does not care whether it rang.
He built the first version of these tools for his own companies. Not to sell. He wanted to know whether the marketing was actually working, and he wanted the answer in a form he could do something about before lunch.
That is still the test. The geo grid, the review engine, the citation checker, the portal: each one exists because a company he runs needed it on a Tuesday morning. A software shop builds what you specify. An operator asks why you are doing it that way first, and about a third of the time that conversation removes a feature instead of adding one.
More about who runs thisFAQ
No. A build stands on its own. Plenty of businesses that need an internal tool do not need us touching their Google profile, and we are not going to bundle one to sell the other. If both make sense we will say so and price them separately so you can see which is which.
You stop. You keep every phase we have already handed over, including the data and the export, and you do not owe the phases we have not started. We would rather lose the back half of a build than talk you through a finish you do not want.
We do, on the platform this whole company runs on. That is why a build here starts from a working portal, a working auth model, and a working database instead of an empty repository, and it is most of the reason the number is what it is.
Yes, and sometimes that is the right answer. If you have someone who knows your stack, we will hand them a punch list and stay out of it. We would rather be useful for one call than expensive for four months.
Maintenance and hosting are optional and quoted only where a build needs them. If your tool is finished and does not need us, the correct monthly number is zero and we will say that.
One call. Describe the thing your business does badly and we will tell you whether software fixes it, what it would take, and roughly what it costs. If the honest answer is a spreadsheet and a better habit, that is the answer you will get.
Discovery sets the scope and the number, in writing, before anything gets built.
Talk to Brayden about a build
