🛡

LocalPulse Red Team

Enter hub password to continue.

That's not right. Try again.

LocalPulse go-to-market: the red team

Strategy pressure-test · 29 July 2026 · attacks the plan as it stands after the local-network change

The plan being tested: LocalPulse sells missed-call text-back at $97/mo to Boulder service businesses. Signup and setup are self-serve so the thing runs hands-off. The first customers come from the local network of business owners you've built since moving to Boulder, and warm in-person conversations are allowed. Target is $1K MRR, roughly 10 to 11 customers.

What changed since the 9 July scope lock: you have a real local network now. That retires the risk the original notes called number one (no local network, no local proof, manufactured trust). It's a genuine advantage and it makes the first few customers much more reachable. It also introduces a new risk that's easier to miss, and it's assumption 4 below.

The finding that isn't an assumption anymore

Before the ranked list, one thing needs saying on its own, because it isn't a risk to weigh. It's a settled fact that breaks a locked constraint.

Self-serve, instant setup is not legally possible for business SMS in the US

Since 1 December 2024, carriers block unregistered application-to-person traffic on 10-digit numbers outright rather than just filtering it. To send texts on a customer's behalf, that customer's business has to be registered as a Brand with The Campaign Registry, and their campaign has to be registered and approved.

Each campaign belongs to exactly one Brand, so you can't run all your customers through one shared registration. There's a legitimate ISV path (Telnyx documents it) that lets LocalPulse manage registrations on customers' behalf, but it doesn't remove the per-customer registration. It just puts you in charge of doing it.

Practically: brand approval runs 1 to 3 business days, and campaign review has been running roughly 10 to 15 days in mid-2026 because of submission volume, with some sources reporting 1 to 7 days after brand verification. Either way, a plumber who signs up on Monday cannot legally receive an automated text-back from his own number that week.

This kills "signup and setup must be self-serve, with zero manual onboarding" as written. It does not kill the business. Three consequences follow, and they're all actionable:

1. A free trial is the wrong model here. A trial costs you real money before any revenue (see the fee table) and the customer can't experience the product for one to two weeks anyway. By the time it works, the trial's half over. Charge from day one and use the registration window as onboarding.

2. The paperwork is your moat, not your problem. A solo plumber will not register a brand with The Campaign Registry. He won't know what that sentence means. This is the single most defensible reason for him to pay someone rather than do it himself, and it's a much better answer to "why not just use the cheap tool" than any feature you could build. Lead with it: he gives you his business details once, you handle the rest, and it starts working.

3. Your signup flow needs redesigning around a waiting period. Collect the legal business name, EIN or sole-proprietor details, and website at signup, then set the expectation honestly ("your Boulder number goes live in about two weeks, here's where it's at"). A status page beats silence. Note the EIN has to be at least 15 days old, which matters for any brand-new business.

What each customer costs you before they pay you

Telnyx passes these through at cost with no markup:

ItemCost
Brand registration, sole proprietor$4
Brand registration, standard (includes secondary vetting)$48+
Campaign verification fee (manual vetting, now applies to all new US campaigns)$15
Campaign, standard use case$30 upfront for the first 3 months, then $10/mo
Campaign, low mixed volume use case$6 upfront for the first 3 months, then $2/mo

So somewhere around $25 to $95 per customer in the first quarter, before number rental and per-message costs. At $97/mo that's comfortably covered by month one, which is fine. It's only a problem if you give the product away first.

One piece of good news: sole-proprietor campaigns exist specifically for businesses without an EIN, which is a lot of solo trades. Their throughput caps (1,000 messages/day to T-Mobile, 15/minute on AT&T) are far above anything a one-person plumbing shop will ever send.

Top kill-assumptions, ranked

Ranked by impact if wrong, times likelihood it's wrong, times how cheap it is to find out. The top one is the one to test this week.

Assumption 1

These businesses miss enough calls that $97/mo obviously pays for itself

Steelman: solo trades work with their hands, often at a customer's house, often somewhere loud, often under a sink. They physically cannot answer. A plumber missing four calls a week and converting even one of them into a recovered job at typical trade job values earns back $97 several times over. The mechanism is real and the arithmetic is generous.

Fails if: a typical Boulder solo operator misses fewer than about two calls a week, or the callers who don't get through simply call back later anyway. Either way, the recovered-revenue story stops covering $97/mo and the pitch has no engine.

Evidence to get this week: ask one friendly plumber in your network to open his phone's recent-calls list and count incoming calls he didn't answer over the past two weeks. Then ask what a typical job is worth to him. That's one conversation with someone who already knows you.

Kill criterion: under 2 missed calls per week across the first three owners you ask, or job values low enough that a recovered job doesn't clear roughly $200. If either holds, the wedge is wrong and no amount of go-to-market fixes it.

Cheapest test: the phone-screenshot conversation above. Free, takes ten minutes, and you get to do it with three people you already know.

This is first because it's the cheapest test of the most load-bearing claim in the entire business, and because the scope notes are honest that these owners don't articulate this pain themselves. They want "more customers." Nobody has confirmed the leak is big enough to be worth plugging at this price.

Assumption 2

The warm local network yields 10 paying, renewing customers

Steelman: warm beats cold by an order of magnitude. Ten customers is a genuinely small number, and a person who's been actively building a local network in a town the size of Boulder could plausibly know 30 to 50 business owners well enough to have this conversation. Trades people also refer each other constantly, so early customers compound.

Fails if: the network is mostly not owner-operators of the target type. Knowing 40 people in Boulder is different from knowing 40 solo plumbers, salon owners, and similar trades. It also fails if the network converts at the low end: at a 20% warm-to-paid rate, 10 customers needs about 50 conversations.

Evidence to get this week: write the actual list. Names, business, whether they own it, whether they're a service business that takes inbound calls. Not a mental estimate, a written count.

Kill criterion: fewer than 25 named service-business owners on the list. Below that, the network alone can't get you to 10 customers even in a good scenario, and you need a second channel designed and tested in parallel rather than later.

Cheapest test: the written list. Thirty minutes.

The 20% figure above is arithmetic under a stated assumption, not a researched benchmark. Treat it as a way to size the list, not as a prediction.

Assumption 3

$97/mo is a defensible price for this feature

Steelman: $97 is a familiar, easy-to-say local-SaaS number that sits below the psychological $100 line, and it's trivially justified by a single recovered job. It's also low enough that an owner can decide alone without thinking hard.

Fails if: a prospect price-shops. GoHighLevel's Starter plan is also exactly $97/mo, includes missed-call text-back as a built-in feature, and a free snapshot gets that workflow running in under two minutes. You'd be charging the same price as a platform that bundles your entire product plus a full CRM. Worse, the agencies reselling GoHighLevel white-labeled to local businesses are your actual competitive set, they exist in every US city, and they win customers with the cold-calling you've ruled out.

Evidence to get this week: in the same warm conversations, ask what they already pay for anything marketing-related and what they'd expect this to cost. Don't lead with your number.

Kill criterion: if owners anchor below $50 without prompting, $97 is wrong at the low end. If nobody blinks at $97 and two or more say some version of "I'd pay more if you just handle it," it's wrong at the high end.

Cheapest test: one question inside conversations you're already having.

My read: matching GoHighLevel's exact number is the worst available position. You get neither the "obviously trivial, just say yes" effect of a much lower price nor the margin and seriousness of a higher one, and you've handed any prospect who Googles for ten minutes a direct comparison you lose on features. The done-for-you compliance work and the local relationship are worth more than a self-serve tool, and the pricing should say so. This is worth deciding deliberately rather than inheriting.

Assumption 4

Winning warm-network customers tells you the hands-off model works

Steelman: revenue is revenue, proof is proof, and early customers of any origin give you testimonials, case studies, and the local credibility the original notes said you lacked. Using an advantage you have is not cheating.

Fails if: you personally shepherd the first five customers, hit roughly $500 MRR, and conclude the model is working. It isn't, yet. You'll have proven that Annette can sell to people who like Annette, which is exactly the high-touch business the scope rules out. The network is finite and non-renewable. It gets spent once. If it produces five customers and then runs dry, you're back at zero with no tested acquisition channel and a year gone.

Evidence to get this week: nothing to research, this is a discipline you build in now. Make every warm customer go through the real signup flow themselves while you watch and stay quiet. Write down every place they get stuck, confused, or need you.

Kill criterion: if a warm, motivated owner who likes you personally cannot complete signup without you intervening, a stranger has no chance, and the self-serve channel doesn't exist yet no matter what the dashboard says.

Cheapest test: sit on your hands during the first signup. Free, and genuinely hard.

This is the subtle one and the reason the local network is a mixed blessing. It's a real advantage for getting to first revenue and a real hazard for learning anything. Treat those first customers as your usability lab and your proof, in that order.

Assumption 5

The product works end to end today

Steelman: the scaffold, schema, and auth are built and committed, and the remaining work is wiring rather than invention.

Fails if: nothing has actually sent a text yet. As of the current repo state, LocalPulse has an Astro scaffold, a D1 schema, and Clerk auth. There's no Telnyx integration, no missed-call webhook, no Stripe billing, and no Boulder landing page in the codebase. The last product commit was 17 June.

Evidence to get this week: get one real missed call to trigger one real text to your own phone, on your own number, through Telnyx. That's the whole test.

Kill criterion: not a kill so much as a sequencing check. If this can't be working within a couple of weeks, don't start warm conversations, because interest goes stale fast and you only get one first impression with people you know.

Cheapest test: one end-to-end call to text, using your own registered number.

Registering LocalPulse's own brand and campaign is a prerequisite for this and takes days to weeks, so it's the long pole. Start it now, in parallel with everything else on this page.

What's well-reasoned

Genuinely, and not as a courtesy:

The wedge choice is correct. Missed-call text-back is the right single feature to lead with. It requires zero behavior change from someone who doesn't use software, the value is legible in one sentence, and it works identically for a plumber and a nail salon, which keeps the build generic the way you wanted. Review requests and AI-visibility reports would both have been harder sells to the same person.

Refusing a long build before first revenue was right, and the current state proves it. The scaffold is thin, which is a feature. Nothing significant has been over-built in the wrong direction.

Boulder-first with a generic build is the correct shape. Local trust is the wedge; the software shouldn't care where it runs.

Using the warm network for the first customers is right, now that it exists. The earlier instinct to manufacture local proof through a Boulder landing page and area-code numbers was a reasonable plan B, and it's now plan B rather than the whole strategy. That's a real improvement.

The $1K MRR target is well-chosen. Ten or eleven customers is small enough to be reachable by hand and large enough to prove something. It's a real threshold, not a vanity number.

What I couldn't assess

The size and composition of your local network. This is now the most important unknown in the plan and only you can answer it. Assumption 2 depends entirely on it.

How many target businesses exist in Boulder. I tried to verify a count of solo plumbers and salons in Boulder and could not find a credible figure. Directory listings and the Colorado SBDC's statewide small-business number are the only public data, and neither is specific enough to plan against. Flagging this as unverified rather than guessing. If it matters later, the City of Boulder business-license records are the place to get a real number, since plumbers are licensed.

Whether LocalPulse has an EIN and legal entity yet. You need one for your own brand registration, and it has to be at least 15 days old before it can be used. If that doesn't exist, it's the actual first task and everything else queues behind it.

The state of the Telnyx account, including whether any 10DLC registration has been started, and what a typical job is worth to the specific trades in your network. Both feed the pricing decision.

Verdict

Ship after testing assumption 1, and do not ship self-serve signup as designed

The go-to-market is sound enough to act on, and the local network makes it much more likely to work than it was three weeks ago. Go land warm customers deliberately and by hand.

The single biggest reason to pause: the product currently promises instant setup, and carrier rules make that impossible. The first self-serve signup would break the core promise on day one, in front of someone who knows you. Redesign the flow around a two-week registration window before anyone sees it.

The evidence that would flip the whole thing: three owners in your network reporting they miss fewer than two calls a week. If that's what comes back, the wedge is wrong, and no amount of pricing, positioning, or landing-page work saves it. That's why it's the first thing to check and why it costs you nothing but a conversation.

This week, in order

  1. Ask three people in your network to count their missed calls. Two weeks of recent calls, plus what a job is worth. This is the highest-value hour available to you right now.
  2. Write the network list. Names, businesses, owner or not, takes inbound calls or not. You need the count before you can plan anything past customer five.
  3. Start LocalPulse's own brand and campaign registration with Telnyx. It's the long pole and it blocks the end-to-end test. Confirm the EIN situation first.

The pricing decision and the signup redesign both wait on what comes back from step 1. There's no point designing a flow for a product whose core value hasn't been confirmed by anyone who'd pay for it.

Sources