Discovery Audit · Start here · 1–2 weeks
What a discovery audit produces
Before anyone writes code, somebody has to walk the whole company and find where the time actually goes. This is the shape of that work, taken from a real engagement with a solar installer and stripped of anything identifying.
Method
How it runs
Interview everyone
CEO down to the coordinators. Sales, design, project management, construction, service, procurement, finance, admin, IT. Each person walks through their actual day and names what slows them down.
Map the stack and the handoffs
Every tool in use, what it costs, who touches it, and what happens in the gaps between departments. The breakages are almost never inside a department. They’re at the seams.
Rank it, then build
Each fix gets scoped, priced, and sorted by whether it grows revenue or cuts cost. Then the build starts, connecting what already exists or writing new software where nothing fits.
Deliverables
What gets handed over
Findings
The kind of thing it turns up
A capacity planning tool already included in a subscription they were paying for, unused, while the same job was being done by hand in a spreadsheet.
The handoff from construction to service had no owner. Everyone assumed the other department picked it up.
The same job data typed into three systems by three different people, because none of the systems talk to each other.
Two paid tools doing substantially the same job, kept because different departments adopted them separately and nobody compared them.
Curious what yours would turn up?
An audit runs one to two weeks and ends with a written deliverable set you own, whether or not you build anything with us afterward.