Real tools, real businesses

You do not have to know what to ask for. You have to know what your week looks like.

Six tools Rad built for six businesses. Names withheld, the shape is real. If one of these sounds like your Tuesday, you already have your answer to "what would we even build?" Every one of them kept the system that ran the big job.

Sign shop, three locations

A field survey tool the crew uses from a phone, tied to one job record.

What they run on
A CRM for the pipeline, a point-of-sale system for the money, and a group text for everything else.
The pain
Site measurements, photos and sketches lived in three places and got retyped. The owner could not see all three locations on one screen.
What got built
A mobile survey screen (measure, photo, video, sketch) that writes straight into the job. A projects board. A reporting layer over the point-of-sale numbers.
What stayed
Their CRM is still the system of record. The app sits beside it and does the parts it never did.
Kiln manufacturer

A support desk that drafts answers from their own manuals, and a market desk that watches the competition.

What they run on
A helpdesk for customer questions, a website, and a network of dealers who set their own prices.
The pain
The same forty questions, answered by hand, from memory. No idea which dealer was undercutting whom, or who won the search results.
What got built
Drafts for every incoming ticket, written from their manuals, with a person approving each one. A price watch across about twenty dealers. A search-and-ads view of who shows up when a potter searches.
What they connected
Their helpdesk, with a key they pasted in themselves.
School district bus office

Day-of dispatch: a driver calls out, and the office sees who can cover before the phone rings again.

What they run on
A routing system, a GPS vendor, radios, and a whiteboard.
The pain
Two people covering the same shift by accident. Changes made from the school side that the dispatcher never saw. An end-of-day count that did not add up.
What got built
One screen for the day's changes, by driver or by school. A double-booking guard that refuses the second assignment. Every change recorded, so the escalation count and the summary agree.
What they connected
Their GPS vendor's alerts.
Staffing firm

Every government solicitation, scanned daily, scored for fit, in the inbox by 5am.

What they run on
Two CRMs, a marketing portal, and a person reading procurement sites by hand.
The pain
Bids found late or not at all. Reps asking the same wage-classification question every week.
What got built
A daily scan of federal and state postings, each one scored 0 to 100 with the evidence, de-duplicated, and sent as a morning digest. A prevailing-wage classification lookup that will not guess a number it cannot cite.
What they connected
The federal procurement API, with their own free key.
Law firm marketing group

One scorecard across several firms: what came in, what it cost, from the systems each firm already uses.

What they run on
A call tracker, an intake system, accounting software, and a different mix at every firm.
The pain
Monthly numbers assembled by hand from four exports, with definitions that drifted from firm to firm.
What got built
Scheduled imports from each system into one view, per-firm definitions written down and applied the same way every month, and a raw-data page so any number can be traced to its source row.
What stayed
Everything. Nobody changed how they take a call or send an invoice.
Animal rescue

A rebuilt site around their real photos, with a pet manager the staff update themselves.

What they run on
A website nobody could edit, a donation platform, and social media.
The pain
Adoptable animals listed days late because updating the site meant asking someone.
What got built
A public site with adopt, foster and volunteer paths, and a sign-in-only pet manager: add an animal, mark it adopted, done.
What stayed
Their donation platform and their application forms, linked rather than rebuilt.
What people actually type

Requests do not sound like software. They sound like this.

Filed from inside the app, in the words of the person who noticed. Each one became a change that shipped.

"Flag rush orders on the intake form."A sign shop, a bug-sized change.
"Two of us keep answering the same customer. Show who has it."A support desk, one afternoon.
"Stop retyping the survey into the quote."The whole reason the tool exists.
"Who is covering Tuesday if Marcus is out?"A question that became a screen.
"Send me the day's changes at 4, not at 6."A one-line change to a schedule.
"Can it pull our jobs table in every morning?"A connection to a system they already had.

Describe how your business runs. About 3 minutes, 8 questions.

You get a written month-one plan for a tool shaped to your week. Free, no call, no obligation. If it reads right, subscribe and the build starts.

Start your build interview