Skip to content

About

Software for the operating loop.

Thorbis builds for the loop a service company actually runs (intake, dispatch, field work, invoicing, payment, follow-up) for the shops the industry's software forgot.

Two people working the operating loop at a desk: laptops, pens, and a marked-up process sheet
Built in Jasper, Georgia, by an operator who ran the loop himself first.

The gap

Who the incumbents built past.

  • Too thin

    The lightweight tools organize a calendar and stall at the fourth truck: no dispatch, no price book discipline, a seat price that punishes hiring.

  • Too heavy

    The enterprise suites bring per-technician pricing, implementation projects measured in months, and a system that needs its own admin.

  • The middle, ignored

    The 3-to-50 technician shop (the family HVAC company, the plumbing contractor with twelve trucks and no dedicated dispatcher) is who this is for.

The principles

Four rules the product is run by.

  • 01

    Operators over admins

    The software does the admin work, or it failed. Nothing here assumes a person whose whole job is feeding the system.

  • 02

    Real data, not demos

    The dry run is your data; the screenshots are the running product; the case-studies page is empty until a story is verified. Nothing is staged to flatter.

  • 03

    One price, full access

    $99 a company, every module, unlimited people. No seat traps, no feature tiers, no quote to decode.

  • 04

    Honest about limitations

    What is not built yet says so, with the roadmap's own words. A limitation you can see is a plan; one you discover after cutover is a betrayal.

Check us

Transparency you can verify, not admire.

  • The price is public

    One company price and a posted rate card for everything metered: on the pricing page, in the structured data, and in the terms.

    The quote
  • The roadmap is public

    Now, Next, and Later, in plain words, and a changelog that logs releases only when they ship.

    The roadmap
  • The stack is public

    Every third party that touches data is named on the subprocessors page: Stripe for payments, Telnyx for telephony, Anthropic for AI, and the rest.

    The subprocessors
  • The security posture is public

    Tenant isolation, processor-held cards, and documentation reviewable before rollout, written down before procurement asks.

    The security page

Start

Built for the shops in the middle.

Easy enough for the first truck, strong enough for a multi-location operation, with transparent pricing and your data staying yours.

Waitlist open. One email when your invite is ready, nothing else.

Coming from a suite? We’ll extract your records.

Rather talk first? Email the team.