CRM and sales decision
FlowBaseHQ
A technical user can realistically build a narrow self-hosted CRM + WebRTC dialer with SMS and basic compliance, but reproducing Flowbase's carrier scoring, Armor protections, native mobile apps, and fully managed 10DLC workflows would be difficult to match.
Visit website↗Built by Patrick Gerrits, who ships 3 products in this index
$29/mo
$348/yr
Read off the official pricing page.
$100one-off160 h to build
$50/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 3 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All FlowBaseHQ alternatives, with the arithmetic →
What a replacement has to do
- Import leads, call leads via a browser dialer (WebRTC), log call events and dispositions in a CRM, and consume credits for talk time.
What it still won’t have
- Carrier spam-status feeds and Armor scoring history
- Score-based caller ID rotation tuned to carrier data
- Built-in 10DLC campaign/brand registration marketplace handling
- Native iOS/Android mobile apps with offline support
- Flowbot AI and any proprietary AI features
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 3 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hostable CRM + browser dialer using: React frontend, WebRTC for calls, Node.js + Express backend, Postgres DB, and Twilio for PSTN/SMS. Core features in scope: leads CRUD with custom fields, import/export CSV with duplicate detection, WebRTC dialer (place calls, VM drop, call events), credits metering and purchase endpoints (simulate payment), SMS send/receive and opt-in/opt-out handling, Google Sheets one-way sync, per-lead consent state and calling-hours enforcement, basic role-based auth, and dashboards for credits and call metrics. Out of scope: carrier spam scoring feeds, mobile native apps, advanced AI features, and multi-tenant enterprise billing. Include error handling, input validation, unit and integration tests for backend APIs, and deployment scripts (Docker + minimal cloud hosting instructions).
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score67
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productFlowbase landing
- official docsFlowbase features
- official pricingFlowbase pricing
- open sourcekrayin/laravel-crm
- open sourcefrappe/crm
Integrity checks
What held up, and what did not.
