ground—work

Your team decided this three months ago. Nobody remembers why.

Groundwork is the memory layer for seed-stage product teams: every decision logged with its reasoning, every piece of research connected to what it changed.

If only “why was this decided?”
ever had an answer.

There is no single switch,
but there is a system that remembers.

Groundwork keeps the reasoning, the evidence,
and the link between them.

Fast teams forget three things.

The reasoning

A decision made on a call, gone by the next sprint. What survives is the what. Never the why, or what you almost did instead.

The research

Five sharp interviews become a doc nobody opens twice. The next debate starts from opinion again, as if the evidence never existed.

The connection

Nobody can say which piece of evidence changed which call. So the team relearns the same lessons. At full price, every time.

Decision Log. Every decision, kept with its why.

Say what happened in one field: Groundwork drafts the entry, you confirm and edit. Reasoning, alternatives considered, who was in the room. When your board asks what shipped and why, the update writes itself.

  • Capture from a braindump, a Slack message, or a meeting transcript
  • Closed / Open / Revisit, with reminders when it’s time to look again
  • Board-ready updates generated from the log, not from memory

The real problem isn’t running the session.

Research Assistant. Know what to ask, before you ask it.

For most first-time researchers, the question itself is the hard part. A hypothesis phrased as a leading question. A usability task written to flatter the design instead of testing it. Get the question wrong and you walk away confident in the wrong thing, and build accordingly. Groundwork writes the sharp version instead: a falsifiable question, not a leading one, sequenced the way a trained researcher would ask it.

  • Every question stress-tested: falsifiable, not leading, built to surface a story
  • Usability tasks scored for real friction, not “did they like it”
  • Synthesis quotes only what participants actually said. No filling gaps with hope

A chatbot writes your research plan once and forgets it ever existed. Groundwork remembers what you learned, who said it, and which decision it changed. And the memory compounds every week you use it.

Capture

Decisions logged as they happen. Research saved the moment it’s made.

Connect

Evidence attaches to the decisions it informed. Linked, not filed.

Compound

The memory grows weekly. New teammates onboard from the log.

Questions, answered.

Who is Groundwork for?

Seed to Series A product teams, roughly 10 to 40 people, where decisions and research start slipping through the cracks as the team grows. If you’re a founder or PM who keeps answering “why did we do it this way?” from memory, it’s for you.

When do I get access?

We’re inviting teams off the waitlist in small batches. The questionnaire when you join helps us find the closest fit first. Those teams hear from us within days, not months.

What will it cost?

Free during early access. After that: per-seat pricing for the Decision Log and a flat monthly price for the Research Assistant. Early-access teams keep a discount.

Where does my data live?

In an encrypted Postgres database, isolated per workspace. Your decisions and research are never used to train models, and meeting transcripts are only pulled when you explicitly connect and select them.

Does it replace our docs?

No. It links to them. Groundwork is the index of what you decided and learned; your PRDs and docs stay where they are, attached to the decisions they belong to.