O/01
The source code
The codebase is yours. Your developers, or any developer you hire later, can read it, change it and deploy it.
Ronin Inc / Custom CRM
Ronin Inc builds custom CRM software your business owns outright: the source code, the database, and the infrastructure it runs on. Add every employee, contractor and partner who needs access. There is no per-seat fee, because nobody is renting you the seats.
Stop paying rent on every login.
01 / The per-seat problem
Salesforce, HubSpot and most hosted CRMs bill per user, per month. The invoice grows with your headcount, not with the value the software delivers.
A seasonal rep, a part-time dispatcher or a new location manager each becomes another monthly line item. Teams respond the predictable way: they share logins, ration access, and keep side spreadsheets for the people who did not get a seat. The CRM stops being the system of record, and the reports built on it stop being true.
Meanwhile the data sits in the vendor’s database, in the vendor’s schema, behind the vendor’s export tools and API limits. Leaving means a migration project, so most businesses stay and keep paying.
A custom CRM changes the math. You pay to build the system and to run it, not to let people log in. The hundredth user costs what the first one did: nothing extra.
02 / Seat-cost estimator
Enter your seat count and the per-seat monthly price from your current CRM invoice. The estimate is seats × price per seat per month × 12 months × 3 years.
A custom CRM is priced by quote after scoping. You pay for the build and for hosting it; the seat count stops mattering.
03 / What you own
The codebase is yours. Your developers, or any developer you hire later, can read it, change it and deploy it.
Your records live in a SQL database that is the source of truth, not a vendor’s black box. Query it, export it, back it up on your schedule.
The CRM runs on infrastructure you control, in accounts held in your company’s name. No vendor sits between you and your operation.
Owned authentication with roles you define. No third-party identity service and no per-user billing.
Features get built because your operation needs them, not because they made a vendor’s release notes.
There is nothing to leave. No lock-in, no rent, and no renewal negotiation hanging over your customer data.
04 / What goes in it
A custom CRM is not a blank database. It is the system of record for the work your team already does, shaped to your pipeline instead of a generic one. Typical builds combine:
05 / Architecture
Ronin’s own CRM, the one behind the booking form on this site, runs as a single Cloudflare Worker with a D1 SQL database. One deployable unit serves the public site, the booking API, the admin sign-in and the gated CRM API. There is no fleet of servers to patch and no stack of SaaS tools stitched together with webhooks.
Client CRMs are built on the same house standard, and the architecture is fitted to the business:
Access is checked on every sensitive request: who is asking, what they may do, and whether the record is theirs. Authentication is not authorization, and private data fails closed. Read the security doctrine.
06 / Rented vs. owned
07 / How a build works
We look at how your business runs today: the CRM you pay for, the spreadsheets around it, the handoffs that break.
We write down exactly what gets built, in what order, how your current records move over, and what you own at the end. The quote is set against that scope.
Ronin and Solomon build it on infrastructure you control, and prove it with real use before anything ships.
The code, the data and the database are yours. No lock-in, no rent, no per-seat fees.
Questions
It depends on your seat count and how long you keep the system. Per-seat licenses recur every month for as long as you use them. A custom CRM has a build cost and a running cost, and neither one grows when you add users. Use the estimator above to see your current seat spend, then compare it with a quote.
Yes. You own the code, the data and the database. There is no license fee to keep using your own CRM and no vendor between you and your operation.
Yes. It runs on infrastructure you control, in accounts held in your company’s name, so your customer records do not sit in a vendor’s shared platform.
As many as your operation needs. There is no per-user billing. Access is controlled by the roles you define, not by how many seats you bought.
Moving your existing records is part of scoping. We map the objects and fields you use today to the new system and plan the import before the build starts.
Yes, through Solomon, Ronin’s governed runtime. Automations propose actions, nothing that sends, spends or writes to an outside system runs without approval, and every step is logged. See AI agent governance.
Next step
Book a consultation and bring your current CRM invoice. We will scope the system your team needs and quote it. Agencies that want to sell these systems under their own name can partner with us on a white-label basis.