ModCuts Barbershop2026
Two locations, one codebase, and a gate that remembers
A two location rebuild where every route, menu, schema block, and booking link is generated from a single locations file, so adding a third shop is one array entry.
Service
Workflow automation and internal tooling
CRM wiring, integrations, and internal tools that remove the spreadsheet and the double entry between the systems a business already runs.
Most operations problems in a growing company are not strategy problems. They are the same customer record typed into three systems, a handoff that depends on somebody remembering, and a monthly report assembled by hand from exports.
Mapping what actually happens
The documented process and the real process are usually different, and the real one is the one worth automating. We watch the work as performed before proposing anything, because automating the documented version produces a tool nobody uses.
Building to the systems you have
The platform stays yours. We integrate the tools already in place rather than proposing a migration, because a CRM replacement is a much bigger project than the problem usually justifies and it puts the customer history at risk.
Where nothing off the shelf fits, we build the internal tool. Where something does fit, we will tell you to buy it.
Failure is designed in
An integration that breaks quietly is worse than no integration, because the business keeps trusting it. Connections are built so a failure raises an alert rather than dropping records where nobody looks.
Related work
Where this has run.
Questions
What gets asked about this.
Do we have to change CRM?
No. We build to the CRM you run. Replacing it is a much larger project and it is rarely the actual problem.
What systems do you work with?
HubSpot, Salesforce, Shopify, QuickBooks, Booksy, and most tools with a documented API. Where there is no API we will say so rather than building something fragile on top of screen scraping.
How do you decide what to automate?
We watch the process as it is actually performed. The steps worth automating are the ones done frequently, the same way every time, by someone whose time is worth more elsewhere.
What happens when a vendor changes their API?
Integrations are built with the failure path defined, so a broken connection surfaces as an alert rather than as silently missing records. Maintenance is a named part of the engagement, not an assumption.
Is this a one time project or ongoing?
The build is fixed scope. Whether it needs ongoing work depends on how many systems it touches and how often those systems change.
Book a scoping call.
45 minutes. You leave with a module breakdown and a rough range, whether or not you engage us.