CRM and sales decision

gosimless

A single developer can build a narrow replacement that provisions numbers, routes SMS-to-email and exposes a portal (using Twilio/Stripe), but reproducing gosimless’s global number inventory, carrier relationships, support for verification edge-cases, and operational scale is non-trivial and outside one-person scope.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off80 h to build

$40/mo6 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Purchase or provision a virtual phone number, route inbound SMS to an email inbox and web UI, allow call-forwarding configuration, and provide logs/CSV export via a control panel.

What it still won’t have

  • Global number inventory and carrier relationships (scale/coverage)
  • Established support and hand-holding for verification edge-cases (WhatsApp shortcodes, alphanumeric senders)
  • Brand trust and existing customer base
  • Operational telephony compliance, fraud detection, and negotiated call/SMS rates

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

gosimless does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a minimal virtual-number service using Next.js + TypeScript for the frontend, Node.js (Express) backend, Postgres for logs, and Twilio (or similar) for telephony. Core features in scope: user signup/login (email), purchase/provision a UK or US virtual number via provider API, receive inbound SMS webhooks and forward messages to a configured email (SMTP/SendGrid), searchable SMS & call logs with CSV export, basic call-forwarding configuration, and billing for number subscriptions (Stripe). Out of scope: negotiating carrier contracts, multi-country number inventory beyond UK/US, and compliance/legal review. Include input validation, error handling, retry for webhook processing, unit tests for API handlers, and an integration test that simulates inbound SMS webhook to end-to-end email delivery.
How we checked2 sources · 3/3 runs agreed · evidence score 57

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score57

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 · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded