Off-the-shelf stack or self-hosted build: which one should you actually buy?
When a $60/month SaaS subscription is the right answer—and when custom event-driven engineering is the only way to avoid a growth tax.
How Larit Assuance Replaced a Bloated CRM with a Custom Build
Started as a $999 diagnostic. Discovery surfaced why off-the-shelf SaaS would penalize their volume, leading to a dedicated 3-workflow client engine.
Most businesses that sit a 45-minute diagnostic with Neovis should buy an off-the-shelf stack, not a custom build. The default Neovis prescription is 3 to 7 simple tools, total software under $60 a month, set up in four days. A self-hosted engine is the exception: Neovis only scopes one when the discovery call shows that a seat-priced CRM or a metered WhatsApp connector would get more expensive as the firm succeeds. That is the decision we made for Larit Assuance after their AI Tools Assessment, and it is documented in the Larit Assuance case study.
If a vendor leads with “we’ll build you a platform,” ask what the $999 diagnosis found that a $20 Zapier account could not fix. If they cannot answer that in a paragraph, they skipped the assessment.
What is an off-the-shelf stack in a Neovis assessment?
An off-the-shelf stack is a short list of products the team can log into this week: tools such as Claude or ChatGPT, Zapier or Make, Notion or Airtable, Fathom, a shared inbox. Neovis names each one, the monthly price, the setup time, and the hours it is meant to return. The client owns the logins. There is no Neovis platform in the middle.
This is the right output for most owner-led firms of 6 to 30 people. The bottleneck is usually copy-paste, missed follow-up, and status questions — not the absence of a private database cluster.
What is a self-hosted build?
A self-hosted build is a small system Neovis designs and ships on infrastructure the client controls. The client owns the data, the schema, and the workflows. They can edit the system without waiting on a vendor roadmap and without paying per seat or per WhatsApp message as volume grows.
On the Larit Assuance engagement, Neovis assembled six layers that each do one job: a spreadsheet-simple CRM interface (NocoDB), PostgreSQL with database-level triggers, a Python event relayer with a debounce buffer, n8n as the workflow engine, a self-hosted Evolution API for WhatsApp, and Caddy as the reverse proxy on a private CRM subdomain. That is a build, not a subscription bundle.
When should you stay off-the-shelf?
Stay off-the-shelf when three things are true:
- The volume of records is something a normal SaaS CRM can easily hold.
- The messaging volume would not generate an unpredictable per-message bill.
- Someone on the team can maintain a Zapier or Make scenario without a developer.
Also stay off-the-shelf if the real problem is adoption, not architecture. A 12-person law firm that never opens its current practice system will not open a NocoDB instance either. Neovis will say so in the report rather than sell a build to paper over a habit.
When does a self-hosted build become the cheaper path?
A self-hosted build becomes cheaper when price scales with success. Seat-based CRMs and metered WhatsApp Business connectors charge more as you add staff, partners, or conversations. For a loan and insurance DSA with a constant inbound of files and sub-agents, that curve is the product. Paying it is a tax on growth.
It also becomes the right path when the workflow is event-driven and the current “CRM” is a static table. If nothing fires when a lead is completed or a stage changes, no amount of extra SaaS seats creates a first WhatsApp in under 5 seconds. That is what the Larit Assuance discovery call surfaced: data sitting still, no triggers.
What did the Larit Assuance diagnostic actually change?
Larit Assuance came to Neovis for the $999 AI Tools Assessment. On the recorded call we walked a typical week and found five things: new leads sat idle, document collection trickled in because borrowers were not told what to send, the office lived on “where is my file?” calls, partners had no payout visibility, and the standard SaaS fix would have billed more as the book grew.
Neovis did not hand them a 7-tool stack. We scoped a Done-For-You build, credited the $999 against it, and shipped three production workflows the client owns: an instant WhatsApp welcome with a product-specific document checklist, real-time stage updates that remove the status-check call, and a Monday partner-payout statement. After handoff: lead-to-first-touch under 5 seconds, 60% faster document turnaround, 80% fewer inbound status calls, and $0 in recurring per-seat or per-message software fees.
Neovis diagnosed, decided to build, shipped, and handed over. Larit Assuance is the beneficiary. They did not build this themselves.
Off-the-shelf vs Self-hosted, Side by Side
| Dimension | Off-the-Shelf Stack | Self-Hosted Build |
|---|---|---|
| Typical Neovis path | Default. ~80% of assessments. | Exception. Only when discovery proves the operational tax. |
| Entry offer | AI Tools Assessment, $999 | Same assessment, then Done-For-You ($999–$4,999, fee credited) |
| Who owns the data | The SaaS vendors you log into | The client, on infrastructure they control outright |
| Monthly software fees | Target under $60/mo total | Hosting only. No per-seat or per-message SaaS penalty |
| Time to first win | 4-day quickstart implementation | First workflow live in under a week after scope locks |
| When you need this | Admin is copy-paste, missed follow-ups, and inbox drag | Volume, sub-agents, or messaging metering would punish growth |
| When to refuse this | A $20 Zapier connector already solves the bottleneck | Nobody on staff will touch a schema, and volume is low |
| Proof on neovis.xyz | The assessment diagnostic process | Larit Assuance Case Study (80% fewer status calls) |
The Six Parts of a Custom Operations Engine
The Larit Assuance system is six moving parts, not one bloated proprietary platform.
CRM Layer
Staff log leads, update stages, and manage connector records in a spreadsheet-simple, responsive UI.
Database
Database-level triggers (trg_lead_complete, trg_stage_updated) that fire instantly on change, not on polling.
Event Relayer
Lightweight service with a debounce buffer so automated triggers do not fire mid-keystroke during data entry.
Workflow Engine
Validates and structures payloads, matches borrower rules, and dispatches the exact template by product category.
Messaging Gateway
Self-hosted WhatsApp connectivity without recurring per-message or per-session third-party SaaS charges.
Reverse Proxy
Automated TLS certificate management, security headers, and high uptime in front of the private CRM server.
Does a custom build mean you skip the $999 assessment?
No. Every Neovis engagement starts on the same rung. Larit Assuance started as an AI Tools Assessment. The build decision came after the transcript showed that off-the-shelf would paper over the problem and then bill for the privilege.
If a firm asks Neovis to “just build it,” we still run the 45-minute diagnostic. Most of the time the report will send them back to a $60 stack. That is a successful assessment.
Who owns the system after a self-hosted delivery?
The client owns 100% of it. Schema, workflows, hosting, WhatsApp connection, documentation. Neovis hands it over after end-to-end testing. There is no required retainer to keep the lights on. The AI Concierge retainer exists for firms that want ongoing advice. It is not a hostage arrangement on the codebase.
How should an owner decide this week?
Book the assessment if you can describe a week of admin and you want a written call on tools versus a build. Do not start with a custom-engine RFP. Do not start with another free readiness quiz.
Use this rule in the meeting with yourself: if the pain is messy handoffs in a firm that will not 10x message volume, buy the off-the-shelf stack. If the pain is idle leads, status-call load, partner visibility, and a SaaS bill that rises with every new file — the Larit Assuance shape — expect Neovis to argue for a system you own.
Book the AI Tools Assessment at neovis.xyz/operations. If the report cannot find 5 hours a week, the $999 comes back.
Frequently Asked Questions
Is n8n always better than Zapier?
No. Zapier or Make is the right connector when your workflows are simple and data can live in existing SaaS subscriptions. n8n is the right engine when events live in a database you own and you want to eliminate per-task billing.
Will Neovis host this for us forever?
No. A self-hosted build runs entirely on infrastructure you control. Neovis handles full implementation, testing, and handoff. Hosting is not a proprietary recurring Neovis lock-in.
Can we start off-the-shelf and migrate later?
Yes. That is the standard path. The assessment prescribes the 4-day quickstart plan first. A custom build is only scoped when volume and seat mathematics make migration the more economical choice.
Lead Operations Consultant at Neovis. Jacob conducts discovery diagnostics with owner-operators to map administrative bottlenecks and engineer zero-overhead automation stacks.
Connect on LinkedIn →Get an objective diagnosis for your business
We diagnose the bottlenecks on a 45-minute call and tell you honestly whether you need a $60 stack or a custom build. Reclaim 5+ hours per week or get a 100% refund.