Is Chassis only for engineering work?

No — operations is a first-class use case. Leave github_repo empty on a project and Chassis runs in operations view: projects with status, milestones, owners, kanban, cycles. Use it for partnership rollouts, hiring drives, pricing changes, vendor onboarding, infra migrations, anything that doesn't have a single repo behind it.

How do Centerline bearings become Chassis projects?

From the Centerline quarterly bearings view, click 'Promote to Chassis project' on any bearing. The bearing title, owner, due date, and description become a new Chassis project. You add milestones and tasks below. Future updates to the bearing keep them linked — the bearing card on Centerline shows live progress from the Chassis project.

Can a non-technical operator use Chassis?

Yes. The operations view has no GitHub clutter, no markdown requirements, no JQL. Setup overhead is intentionally low: open the Drive, Forge scaffolds a starter project from your venture profile, you start moving tasks across the kanban. Most operators ship work the first day.

Does Chassis replace Asana for operations work?

For most small-team ops use cases, yes. The cockpit-native posture wins: owners are Crew records, projects link to Atlas docs, quarterly cadence comes from Centerline, Forge writes weekly digests. Where Asana still wins: deep custom fields, mature portfolio rollups, intake forms. See /chassis/vs-asana for the honest breakdown.

How does Chassis handle hiring drives?

Hiring is a project: 'Hire Senior Backend Engineer' with milestones (sourcing, screen, on-site, offer). Tasks against each candidate. Owners are Crew records. The Onramp Drive (separate, in the OPS bundle) handles the candidate-pipeline depth — applications, scorecards, scheduling. Chassis is the project wrapper that ties Onramp work to the operating cadence.

Does Chassis pricing scale for an operations team?

Yes. Chassis is $49/mo flat per tenant, no per-seat. The OPS exec bundle ($299/mo) includes Chassis + Centerline + Crew + Gauge + 5 more Drives — typically the right pick because operations work touches all of them.

← CHASSIS USE CASE · OPERATIONS TEAMS

Chassis for operations teams.

The project layer for everything that doesn't fit on a quarterly bearing — partnership rollouts, hiring drives, pricing changes, vendor onboarding, infra migrations. No GitHub repo required. Owners are real people from Crew. Centerline bearings promote in without re-keying.

Bundled with the OPS exec hire ($299/mo) — a COO-shaped exec that runs Chassis, Centerline (cadence), Crew (people), Gauge (instrumentation), and four more Drives as one operations surface.

The job.

Operations work is the work that doesn't have a single repo behind it. A partnership rollout: legal review, integration scoping, joint marketing copy, launch announcement, post-launch retro. A hiring drive: source, screen, on-site, offer, onboarding. A pricing change: model the new tiers, update the marketing site, migrate billing, write the customer email, monitor churn for two weeks. An infra migration: vendor selection, contract negotiation, technical migration, comms, decommission.

The work spans weeks or months, touches multiple owners, depends on artifacts that live elsewhere (a contract in Atlas, a candidate pipeline in Onramp, a metric in Gauge). Tradition handles this with spreadsheets, Notion docs, project-tracking sprawl across three tools. The seams are the same as engineering's: status drifts, the weekly review pulls from a stale source, the retro never happens because nobody owns writing it.

Chassis is the project wrapper. Status, owner, due date, milestones, kanban tasks. The cockpit gives it the wiring the standalones can't: owners are Crew records (one canonical employee), tasks link to Atlas docs (the contract, the runbook), Centerline bearings promote in (so the quarterly cadence and the breakdown share a substrate), Forge writes the weekly digest (so leadership sees what shipped without anyone burning a Friday afternoon on it).

It is opinionated, not configurable. That is the point. Operators don't want to spend a week building a custom Asana template; they want a kanban that already understands what a quarterly bearing is (what EOS calls a rock).

How Chassis fits the operations workflow.

Projects without a repo.

Leave github_repo empty. Operations view: status (active / on-hold / done / canceled), owner, due date, description. Milestones with hit/missed states. The four-column kanban (To-do / Doing / Blocked / Done) for tasks. No engineering-shaped clutter.

Milestones for the long arc.

A partnership rollout has five milestones: scoping, legal, integration, launch, post-launch retro. Each carries a date + owner + done/missed state. Milestones surface to Centerline as the project's "where it is in the arc" — leadership sees the rollup without drilling into tasks.

Owners are Crew employees.

Task owner = a Crew record. The same person record HR, payroll, performance reviews, onboarding all reference. When someone leaves the company, ownership reassigns at the Crew layer and Chassis follows. When you hire, the new person is available as an owner the day they sign.

Atlas-doc links on every task.

A vendor onboarding task links to the contract in Atlas. A pricing-change task links to the model spreadsheet. Forge searches Atlas when scaffolding subtasks, so it knows about your runbooks and SOPs. The kanban stops being "where I write things down" and becomes "where I move work that's grounded in what we already know."

Centerline bearing breakdown.

From Centerline's quarterly bearings page, hit Promote to Chassis project. The bearing title, owner, due date, description become a Chassis project. You add milestones and tasks underneath. Future updates link both ways — the bearing card on Centerline shows live milestone progress without anyone copying status between tools.

Forge weekly digest in operator voice.

One click on Insights. Forge writes a weekly progress readout in markdown — shipped this week, heads up next week. Tight, factual, no filler. Paste it into Slack, your weekly review doc, or the digest email. Built for operator voice, not corporate voice.

Workflow walkthrough — a partnership rollout.

Concrete five-step example. Q3 partnership rollout with a distribution partner.

Hire OPS exec, get the bundle. $299/mo, 7-day trial. Chassis + Centerline + Crew + Gauge + 4 more arrive at install. Forge scaffolds a starter project from your venture profile — the OPS exec already knows what your business is.
Promote the Q3 bearing into a Chassis project. "Ship the partner integration" lives in Centerline as a quarterly bearing with an owner and due date. One click promotes it to Chassis. Add five milestones: scoping, legal, technical, launch, retro.
Assign Crew owners per milestone. Legal milestone → general counsel record in Crew. Technical milestone → engineering lead. Launch milestone → marketing lead. Owners are real people; ownership flows when the org changes.
Run the kanban against vendor responses. Tasks on the To-do / Doing / Blocked / Done board. "Send draft contract redlines" / "Schedule integration scoping call" / "Draft joint launch copy." Forge can suggest 3–5 subtasks on any big task — break "Joint launch announcement" into press release, email blast, social copy, partner co-blog, post-launch retro.
Close project, get auto-retro. Mark the project done after the post-launch milestone. Forge writes the retro — what shipped, what slipped, keep / cut / start — grounded in the activity log. Edit, ship to the leadership weekly review, the bearing closes on Centerline.

The other Drives that come with this.

Operations work touches every system in the cockpit. Three Drives in the OPS bundle that pair tightly with Chassis.

OPS exec — the COO-shaped exec. Operates Chassis, Centerline, Crew, Gauge, and four more (Onramp, Cohort, Relay, Affiliation) as one operations surface. Runs your weekly + quarterly review, drafts the weekly digest, surfaces what's blocked. $299/mo for the whole bundle.
Centerline — operating cadence. Weekly review, quarterly bearings, scorecard. Centerline runs the cadence; Chassis runs the breakdown. Bearings promote into projects without re-keying.
Crew — the people layer. Employee records that every Drive references. Task owners on Chassis projects are Crew records, not free-text emails. When someone leaves, ownership reassigns at the Crew layer and Chassis follows automatically.
Gauge — instrumentation. The metrics layer. Project completion events emit to Gauge so leadership dashboards see what shipped. Pricing-change projects automatically wire to revenue metrics, hiring drives wire to headcount metrics.

PRICING

Pricing for operations teams.

Standalone Chassis — $49/mo. Just the PM Drive. Right if you already have your own ops lead and only want the project layer.
OPS exec — $299/mo. COO + 8 specialists. Includes Chassis + Centerline + Crew + Gauge + Onramp + Cohort + Relay + Affiliation. Right pick for most ops-led teams.
Full C-Suite — $599/mo. All five execs, every Drive in the box.
7-day free trial on first install. Cockpit itself is free. Annual billing saves 20%. Per-tenant pricing — no per-seat surprise.

Run operations on Chassis.

Get started Back to Chassis See pricing