Selected work · Our own product

Operlyn

We built and operate a multi-tenant SaaS product, so our product decisions are tested against production constraints, billing, carrier rules and day-to-day support.

The problem before

The work had no shared operating layer.

Home-service contractors can miss inbound calls while they are on a job, leaving customer inquiries waiting.

What we built

  • Missed-call text-back within seconds and a two-way SMS inbox
  • Review requests with two-step sentiment and a lead pipeline
  • Stripe billing plus Twilio and Telnyx number provisioning
  • Hardened edge functions with rate limiting

How it works

A clear path through the process.

  1. 01

    A customer places an inbound call

  2. 02

    A missed call triggers a transactional text

  3. 03

    The conversation continues in one inbox

  4. 04

    Consent and delivery events stay recorded

Stack

ReactPostgresTwilioTelnyxStripe

What this means for you

Build around the handoffs.

We understand the unglamorous production work—permissions, billing, messaging rules and failure handling—because we run software ourselves.

Ops Teardown · $490

Map the system your team needs next.

Bring the workflow that wastes the most time. Leave with a clear map and a fixed-price next step.