STATION 0.0000 · THE BOARD
Tell us what you're building. We'll tell you what you can put down.
Six channels on one board: a founding-access request, a founder on the line for migrations and larger rollouts, a security desk that returns the trust pack, a support line tied to the public status page, press, and careers. Pick the line. We log the call.
The board, in section
Who it's for — founders and early teams who want in before the public launch.
- Channel
- request access and we onboard you by hand. contact@horz.dev.
- Response
- we read every request, and a founder replies in person. No waitlist autoresponder, no queue.
Get in before the doors open.
Who it's for — teams and larger companies replacing a drawer of point tools — a helpdesk seat here, Rippling there, a bookkeeper, three analytics dashboards that disagree. Multi-layer rollouts, a migration off what you already run, multiple entities, a data-residency requirement, and the procurement and security review that come with all of it.
- Channel
- a founder, by call or thread. talk@horz.dev, or book a slot [PLACEHOLDER]. Not an SDR, not a drip sequence.
- Response
- first reply within [PLACEHOLDER — target: one business day]. A founder answers this line, not a queue.
The seven layers don't change with headcount. The bigger the back office, the more of it you hand back, and the terms get drawn to fit.
Hand back the whole back office, at any size.
Who it's for — security, legal, and procurement running a vendor review before a pilot can start.
- Channel
- security@horz.dev. The desk and the controls live at /security.
- Response
- first reply within [PLACEHOLDER — target: two business days].
Ask and we send your trust pack: the SOC 2 Type II report, the signed GDPR Article 28 DPA, the sub-processor list, and a recent pen-test report, all [verify before launch]. We complete your questionnaire. The review happens before the pilot, not after it.
Clear the review before the pilot.
Who it's for — existing customers with a layer to fix or a question mid-run.
- Channel
- in-app, or support@horz.dev. Live state on the public board: status.horz.dev.
- Response
- first reply within [PLACEHOLDER]. The layers fail independently, so the status page reads per layer.
Read the board before you write. status.horz.dev tells you whether the issue is yours or ours.
Check the board first.
Who it's for — media and analysts.
- Channel
- media@horz.dev. The brand kit lives at [PLACEHOLDER].
- Response
- first reply within [PLACEHOLDER].
Pull the brand kit; ask us the rest.
Who it's for — people who want to build the thing that lets a company stay small.
- Channel
- careers@horz.dev. Open roles at /careers [PLACEHOLDER].
- Response
- we reply when a role is open. [PLACEHOLDER]
We run lean on purpose: the back office is offloaded to the product we sell, so we hire only into the core. Roles post when the core needs them.
We hire into the core only.
Objections
You won't get one. The Talk-to-us line is answered by a founder, not a queue, and there is no drip sequence behind the form. If you'd rather not get on a call, request founding access instead and we'll set you up by hand.
No. The standing is scale-agnostic: the bigger the company, the more back-office headcount it can hand back. Migrations off a sprawl of point tools, multi-layer rollouts, multiple entities, a data-residency requirement, and procurement all run through the Talk-to-us line. The seven layers don't change with size; the terms get drawn to fit.
That is the Security & trust line. Ask and we send the trust pack: the SOC 2 Type II report, a signed GDPR Article 28 DPA, the sub-processor list, and a recent pen-test report, all [verify before launch]. Then we complete your questionnaire. The full controls live at /security, and the review happens before the pilot.
The Support line, and the public board first. status.horz.dev reads each layer independently, so you can see whether the issue is yours or ours before you write. A Marketing outage never holds up a Delaware franchise filing.
Where this points
Pricing — what each route costs to act on.
See pricing →Security & Trust — the controls and the trust pack, marked and dated.
Read security →Manifesto — why we run the six functions around your product.
Manifesto →Status — the public board, read per layer.
Open status →
The Floor
Request founding access.
06 CHANNELS · 1 BOARD · A FOUNDER ON THE LINE
END OF SECTION · STATION 0.0000