Discovery
Two weeks with the people who do the work. Output: the data model and the first release scope.
Custom CRMs and internal tools
Software shaped like your operation.
When the spreadsheet stops fitting and the off-the-shelf tool never did. Purpose-built CRMs, back-office systems, and operational tools.
Off-the-shelf tools fit the average business. Yours has a process that makes it money, and that process is usually the part the tool cannot model. We build the software around the way you actually work, and we build it to be changed.
- Sheet
- 02 of 06
- Typical shape
- web app, role-based access, audit log, reports
- Output
- a tool your team uses daily, plus its documentation
- Data
- migrated from the current spreadsheet or tool
You might be here because.
Start from the constraint you have, not from a solution somebody already picked.
The spreadsheet has become the system of record and it is fragile.
The CRM you pay for models a sales process that is not yours.
Operations run on a tool with three workarounds per screen.
Two teams keep separate copies of the same data.
A role in the company exists only to move data between systems.
You need permissions, audit trails, and reporting the current tool cannot give you.
What changes
From the spreadsheet to a system of record.
Exports, forms, and the spreadsheet go in one side. Records with owners, stages, and an audit trail come out the other.
Exports and forms in
- contact
- company
- deal stage
- invoice
- audit entry
Records with owners out
What we deliver.
What an engagement can include. Scope is agreed in writing before work starts.
- Process and data model discovery
- Custom CRM and pipeline tools
- Back-office and operations systems
- Role-based access and audit trails
- Reporting and dashboards from the real data
- Import and migration from the current tools
- Integrations with the systems that stay
- Training, documentation, and handover
Ways to engage.
Four shapes the work can take. Most engagements start small and grow into ownership.
First release
The smallest tool that replaces the spreadsheet, shipped to real users.
Iteration
Releases every week or two as the operation reveals what it needs next.
Ownership
Ongoing maintenance and features under one agreement.
How it runs.
Recorded like a drawing's revisions: what changed, and who signed it.
- A
Observe
Sit with the people who do the work and map the real process, not the org chart.
- B
Model
Decide the data model, the roles, and the rules the software must enforce.
- C
Replace
Ship the first slice that replaces the spreadsheet, and migrate the data.
- D
Extend
Add what the operation asks for, in the order it pays off.
Questions
Before we start.
Practical answers about this kind of engagement.
Often you should, and we will say so. Custom tools make sense when the process is the advantage, when the data model does not fit, or when the workarounds have become their own job.
Start a project
Let's build the thing that changes your business.
We reply within [PLACEHOLDER: reply time]. You get a written first step, whether or not you hire us.
Last updated