Almost every CRM startup reaches the same fork: add texting by wiring a CPaaS yourself, or sit a managed layer under it. Twilio is the default for the first option, and it's a good tool. The trouble isn't the API. It's everything around the API that a CRM's customers will expect on day one.

If your roadmap says "texting" next to a two-week estimate, read this before you commit.

What the two-week estimate leaves out

The send call is the easy part. A multi-tenant CRM also needs:

  • A sub-account, number and 10DLC registration for each customer business.
  • Opt-out handling that spans numbers and campaigns.
  • Quiet-hours timing.
  • Inbound routing to the right customer's inbox.
  • A billing story for usage you pass through.
  • Support for the day a carrier rejects a campaign.

Each is a small project. Together they're a team. See what building SMS infrastructure yourself costs for a longer accounting.

Five signs you've outgrown DIY

  1. You're writing a registration workflow instead of CRM features.
  2. Customers ask why their texts show as filtered.
  3. Support spends time on STOP edge cases.
  4. You can't tell a customer's cost from your own cost.
  5. A second compliance requirement just appeared on the roadmap.

One or two signs is normal. Four means the build is eating the product.

What a managed layer takes over

Ready is a texting API for software companies that text on behalf of their customers. Each customer gets a sub-account with its own numbers and registration. Registration is a single line at $25 a month per customer, with the first campaign included, and each number is $2 a month. Most approvals take 2 to 7 days. The send path handles STOP, quiet hours, number validation and TCPA and DNC screening where you switch it on, and you integrate over one REST API with webhooks.

You still own consent capture and your product's UX. Ready doesn't remove those.

Staying on Twilio is right when

  • You need channels Ready doesn't offer, or international reach beyond what it supports.
  • You have the compliance engineering already and want raw control.
  • Per-segment price at very high volume decides it. Raw CPaaS APIs can price at or below Ready's per-segment rate at volume, and Ready has no volume discount.

Be honest about that last point. Our Twilio vs Ready comparison for SaaS texting says the same.

A decision table

Your situationLean toward
Two engineers, ship in a quarterManaged layer
Dedicated messaging teamCPaaS or managed layer
Need heavy customization of routingCPaaS
Many small tenants, each needing registrationManaged layer

Frequently asked questions

Can I start on Twilio and move later?

Yes, but plan the number port and the opt-out history. See the migration mapping for developers.

Does Ready work for a CRM with one tenant?

It's built for several, but a single tenant works too.

The practical takeaway

Estimate the whole build, not the send call. If the list above looks like your next two quarters, read the quickstart and send a test message.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.