Buy the messaging layer and build the product on top of it, unless texting is the product itself. A platform that texts on behalf of its customers can wire up a first send in a day, but the work that follows (registration, opt-outs, quiet hours, per-customer isolation) is a permanent line on the roadmap.

This post is for the CTO or head of product weighing that call. We make Ready, so we have a stake in the answer, and we'll say where building is the right choice. If you only need the cost side of running your own gateway, our explainer on how SMS gateways work goes deeper on that.

What "build" actually means

Nobody builds SMS from nothing. Building means you hold a contract with a messaging provider, or several, and write everything between your product and that provider's API. Buying means a layer like Ready sits in that space and you call one REST API.

So the real question is which pieces you want to own. Sending a text is the easy piece. Here's the full list a platform ends up owning when it builds.

  • Number provisioning for every customer, and the monthly cost of each number.
  • Brand and campaign registration (10DLC) for every customer, with its own review and rejections.
  • Inbound handling: STOP, START and HELP keywords, plus plain-language opt-outs.
  • Quiet hours by recipient area, so a text doesn't go out at 3 AM local time.
  • A consent record, an opt-out list that holds across campaigns, and a way to answer a complaint.
  • Delivery status, retries and idempotency so a retry never sends twice.
  • Isolation, so one customer's sender reputation doesn't pull down another's.
  • A place for replies to land, which is an inbox or a webhook into your product.

The part that takes a sprint

A send endpoint, a webhook receiver and a status table are a sprint or two for a competent team. That's the part that makes building look cheap on a planning doc, and it's real. If you've written a payments integration, you've written something harder.

Here's the shape of a send on a platform you buy. It's one call with two headers, and the second one keeps a retry from texting the same person twice.

curl -X POST https://api.tryready.com/v1/messages \
  -H "X-API-Key: <key>" \
  -H "Idempotency-Key: 6f1c2a9e-4b7d-4c1e-9a52-0d3f8e7b1a44" \
  -H "Content-Type: application/json" \
  -d '{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true}'

You can build an equivalent in-house. The point is that the call is the smallest part of the system behind it. The API quickstart walks through a key, a first send and a webhook.

The parts that never finish

Registration is the clearest example. Every customer of yours that texts needs a brand and a campaign registered with the carriers, and a rejected campaign has to be fixed and resubmitted. If you build, someone on your team learns the use-case rules, the rejection reasons and the throttling that follows approval. Our 10DLC explainer covers the rules, and the registration API guide shows what automating it looks like.

On Ready, registration is one line per customer at $25 a month (the brand and its first campaign), with $20 a month for each extra campaign and $2 a month per number. Most approvals take 2 to 7 days. Ready registers businesses that have an EIN only, so a sole proprietor without one can't register, and that's a limit worth knowing before you promise a customer anything.

Compliance is the second moving part. Rules change, carriers tighten filtering, and a STOP has to be honored across every campaign. Ready honors inbound STOP and UNSUBSCRIBE and also catches clear phrases such as "please stop texting me", though odd wording no list catches still needs a person to read replies. Ready also holds campaigns, drip campaigns and automations up to 24 hours for the recipient's quiet-hours window. Compliance remains the sender's responsibility either way. A layer reduces your exposure; it doesn't remove it.

Build vs buy, side by side

PieceIf you buildIf you buy a layer like Ready
Send endpoint and webhooksYou write and run itOne REST API, documented
Per-customer isolationYour data model and your routingA sub-account per customer with its own numbers and registration
10DLC registrationYou own the forms, the rejections and the follow-upBrand and campaign registration by API or in the app
STOP and opt-out handlingYou write the keyword matching and the shared listHandled on inbound, with an opt-out lookup in the API
Quiet hoursYou compute them by recipient areaEnforced by Ready, with the hold windows above
Provider contract and outagesYou manage it directlyReady sits over a messaging provider and doesn't fail over between providers
Carrier changesYour team reads the noticesReady handles registration changes on its side, though you still see the effects

Notice the last two rows. Buying doesn't make carrier risk vanish, and Ready doesn't fail over between providers. You're trading control for time, and you should price that trade honestly.

What it costs, without a made-up total

Ready's rate is $0.0075 per segment plus a $0.0045 carrier fee per segment, passed through at cost. One flat Standard rate, with no volume discount. The all-in figure is $0.012 per segment and leaves out screening, the per-segment charge ($0.003) for the Scrub lists and Number validation switches when you turn them on. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. Enterprise is custom, so talk to us if you need it. The full list is on the pricing page.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

For a build, the cost isn't a rate. It's the engineers who keep the system current, the provider fees underneath, and the support load when a campaign is rejected or filtered. Raw messaging APIs can price at or below Ready's per-segment rate at volume, so don't buy on the per-segment number. Buy because of what's included, and compare against the honest cost comparison of Twilio alternatives.

When building is the right call

Build if texting is your core product, if you need routing or carrier relationships a layer can't give you, or if you already run a messaging team that owns this work.

Buy if texting is a feature your customers want inside your product, and your team's time is better spent on the product itself. A useful test is to ask who gets paged when a customer's campaign is filtered. If the honest answer is "nobody on our team should have to know how that works," buy.

A hybrid is common too: buy first, learn what your customers need, and revisit once volume and the roadmap justify it. That's a reversible decision. Building first and finding out in month six that registration eats a quarter is harder to undo.

A short decision checklist

  1. Is texting the product, or a feature inside it?
  2. Do you have an owner for registration, opt-outs and carrier notices?
  3. Do you need per-customer isolation from day one?
  4. Can you name the cost of a filtered campaign for one customer?
  5. Does your team have capacity for a permanent compliance workload?

If most answers point to "feature" and "no owner," buy. For the platform angle in detail, read what to check before you embed texting. When you're ready to try it, sign up and send a first text, then judge the layer on what it handles for you.