STATION −0.0750 · PRICING

Priced by how much of the company you hand over.

You pay by the function, not the seat. Four layers, six, or all seven — the count is the price.

07 LAYERS · 06 BRAIN ALWAYS ON · PAY FOR WHAT YOU TURN ON

INCLUSION · 07 STRATASML01 CUSTOMER SERVICE02 LEGAL03 HR04 MARKETING05 ANALYTICS06 COMPANY BRAIN07 TAXFILLED · THE COUNT IS THE PRICE4/76/77/7
01SOLO

Who it's forthe founder who just shipped and is still the entire company. Solo to three.

4 / 7

Founding pricing — set with our first customers.

Talk to us →

Your week goes back to the product.

The support queue, the marketing site, and the metrics, all sitting on one brain that already knows your product. The 2am password-reset ticket gets answered in your voice. The blog ships on a schedule instead of dying after three posts. Every number reconciles to one definition of MRR, not a Stripe CSV that disagrees with PostHog. The functions that face outward run themselves; the only thing on your calendar is the thing only you can build.

Runs · 4/7
01 CUSTOMER SERVICE · 04 MARKETING · 05 ANALYTICS · 06 COMPANY BRAIN
Still yours
02 LEGAL · 03 HR · 07 TAX
02STARTUP— default

Who it's forseed to Series A. Revenue, signed contracts, multi-state filings stacking up, and no one to hand them to.

6 / 7

Founding pricing — set with our first customers.

Talk to us →

The legal and financial spine, without a lawyer or a CPA on payroll.

Everything in SOLO, plus the paper and the filings. A vendor MSA redlined against your playbook before lunch. A GDPR Article 28 DPA issued the day a prospect asks for one. Your Delaware franchise tax filed before March 1, the R&D credit claimed on Form 6765. A licensed attorney signs what gets signed; a licensed CPA or EA signs what gets filed; you authorize the e-file as the officer.

Runs · 6/7
01 CUSTOMER SERVICE · 02 LEGAL · 04 MARKETING · 05 ANALYTICS · 06 COMPANY BRAIN · 07 TAX
Still yours
03 HR
03SCALE

Who it's forgrowth-stage. A team to pay, a drawer full of point tools to retire, the whole back office to put on one backend.

7 / 7

Founding pricing — set with our first customers.

Talk to us →

Hire your tenth engineer before your first HR manager.

The last department joins the stack. Sourcing on one disclosed rubric, offers struck against a current 409A, I-9s and state new-hire reports filed inside the window, every payroll cycle run for your sign-off. Seven vendors collapse into one dependency reading one brain: the offer letter pulls the comp band, the tax return pulls the payroll, the support reply pulls the refund policy. You add headcount to your one vertical, not to the back office.

Runs · 7/7
01 CUSTOMER SERVICE · 02 LEGAL · 03 HR · 04 MARKETING · 05 ANALYTICS · 06 COMPANY BRAIN · 07 TAX
Still yours
your core product. Nothing else.

The inclusion matrix

Reading the grid is reading a section: which of the seven layers each tier runs. The numbers across the top are the layers, 01 through 07.

TIER01020304050607
SOLO
STARTUP
SCALE

filled stratum: run by horz.hairline stratum: still yours.

06 COMPANY BRAIN is in every tier. It is the substrate the other six layers read from and write to; there is no horz without it. The price moves with the count of filled strata above it.

Founding pricing

The model is set: you pay for the layers you turn on, with Company Brain underneath all three tiers. The numbers are not set yet, and we would rather draw them with our first customers than guess at them without you.

Founding customers get a founder on the line, hands-on onboarding, a say in what ships next, and their founding rate held for good. Tell us which layers you'd hand over, and we draw the terms against your real numbers.

Above SCALE

Multiple entities, a data-residency requirement, or volume past what a tier should meter. The seven layers don't change; the terms get drawn to fit. A founder answers, not a queue.

Questions

  • By the function, flat. You pay for the layers a tier runs, not per seat and not per resolved ticket. A support tool that bills per resolved ticket charges you more the more customers you win; a layer you depend on shouldn't. One number, one bill — the whole back office covered.

  • Yes. You already run Stripe, maybe Pilot, maybe Rippling. SOLO is the floor: four functions for the founder who's still the whole company, starting with the ones bleeding the most time, usually the support queue and the marketing site. horz is the backend beneath your existing tools, and it lights up layer by layer as you move up tiers. This is not a rip-and-replace.

  • Those each own one function and can't read each other. horz's layers share one brain, so the contract redline knows your pricing, the support reply knows your refund policy, the tax return reads the closed books. The integration is the product. You're not buying seven better tools. You're buying the one thing seven tools can't be: connected.

  • You move up, which is just lighting a hairline stratum. Nothing re-onboards: the brain, the history, and the connected sources carry over, because they were the foundation the whole time. Outgrowing SOLO means you started taking revenue and signing contracts, so Legal and Tax switch on; outgrowing STARTUP means you started hiring, so HR does. The company changes, the foundation doesn't.

  • You own it. Connectors are read-only by default, your corpus never trains a shared model, and zero-data-retention terms hold with the underlying model providers. Every layer runs under SOC 2 Type II with a GDPR DPA. Company Brain mirrors your existing permissions at query time: if you can't open a document in Drive, the brain won't quote it to you.

  • The whole back office on one young vendor is the right thing to worry about. Three things answer it. The artifacts are already yours: a standing export of the company graph, plus every filed return, signed contract, and resolved thread the layers produced (see cancellation, below). The accountability is human: a licensed CPA, EA, or attorney signs what gets filed or signed, as a real party of record, not a model. And the layers fail independently behind a public status page, so a Marketing outage doesn't hold up a Delaware franchise filing. Connectors stay read-only, so Stripe, Drive, and your helpdesk keep running with or without us.

  • Cancel anytime, no exit interview. You keep the artifacts the layers produced: the filed returns and workpapers, the signed contracts, the resolved threads, the approved metric definitions, and an export of the company graph. They were yours when they were drafted, and cancellation doesn't claw them back. A backend you can't walk away from isn't one we'd want to sell.

  • No. A bundle is seven products behind one invoice. horz is seven functions behind one brain. A support tool can't read a legal tool; a bookkeeper can't read your inbox. Our layers write to and read from the same graph, so each one is informed by the other six. The bundle is the failure mode we are built against.

  • horz drafts and runs; you stay on the signature line. Nothing gets signed or filed without a licensed human there: a CPA or EA signs the return, an attorney signs the contract, and you authorize the e-file as the officer. Each layer produces a named, reviewable artifact with the source behind every line. We under-claim on purpose.

The Floor

Tell us what you'd hand over.

07 LAYERS · 06 BRAIN ALWAYS ON · THE COUNT IS THE PRICE

END OF SECTION · STATION −0.0750