For foundersStartup operations

Startup operations, from pre-seed to Series A

The first pilots bring support tickets, a weekly report for each customer, and contracts on five different sets of terms. Get them set up around the product, with AI doing the sorting and drafting, until you hire the person who will own them.

The Boston Dynamics Support Center homepage: search, then Spot, Orbit and Stretch
In practice · Boston Dynamics · 2024 The Boston Dynamics Support Center rebuild Read the case study
By stage

What to set up now, and what can wait

Each round brings a different set of operations work. Set up the cheap parts early, because they get expensive to fix once customers depend on them.

  1. 01 · Pre-seed

    Before the first customer

    A shared inbox for customer questions, so they stop arriving in a founder's personal email. One folder for every signed agreement. A written list of what each pilot customer was promised. Books that keep their history when something changes. All four fit in tools you already pay for, and the rest can wait for the first paying customer.

  2. 02 · Seed, first pilots

    When customers start calling

    A support site with the manuals and known issues, so tickets stop landing on engineers. A weekly report for each pilot customer, built from the data the product already records. Each contract's terms and billing in one place. Onboarding that gets a new customer through setup without a founder on the call.

  3. 03 · Series A

    Before the first operations hire

    Each process written down, the tools under it wired together, and the numbers a new head of operations will be asked for on their first day. The person you hire starts from a system they can change.

Proof

Operations started from scratch, more than once

Your engineers stay on the product. The work around it has been done before, at Boston Dynamics, Uber and BeBetween.

Common questions

When does a startup need help with operations?

When operations work starts landing on the founders and the engineers: support tickets, the pilot report someone rebuilds every Friday, the first contracts on different terms in a founder's inbox. It tends to arrive with the first pilots, a few months after a seed round.

Is this a fractional head of operations?

Close to it. Embedded with your team keeps one person working with you month to month on the operations around the product, and the tools those operations need get built as part of it. When you hire a head of operations, they start with written processes and tools that already run.

We're pre-seed and not ready for outside help. What's worth doing now?

A shared inbox for customer questions, one folder for every signed agreement, a written list of what each pilot customer was promised, and books that keep their history. All four fit in tools you already pay for. The rest can wait for the first paying customer.

Where does AI fit in early-stage operations?

Inside the processes, once they're written down. An agent answers the support questions your documentation already covers and hands the rest to a person with the history attached. Pilot reports get drafted from the data the product records. Contract terms get pulled into each customer's record when the agreement is signed.

Do you work with startups outside Boston?

Yes, remotely, across the US. Teams in Boston and Cambridge can also meet in person.

Next step

What landed on your engineers this week?

Bring the pilot about to go out, or the round you just closed. If it's early for outside help, you'll still leave the call with what to set up first and what can wait.