Stop shipping from stale context

    Turn software conversations into approved specs.

    Freshbase captures product and engineering conversations, proposes decisions, requirements, and acceptance criteria for review, then keeps approved context synced with your docs and Linear.

    See the Inbox flow
    AI proposes. Team approves.Context becomes reusable.Linear stays synced.
    SESSION
    Fri, Apr 1713:45 · 30minGoogle Meet8 participants

    Freshbase summary

    Context layer review & V1 positioning

    • Freshbase turns product conversations into approved specs before work fans out
      • Meetings produce proposed decisions, criteria, and ADR updates
      • Human review in Inbox stays as the gate before shared context changes
      • Docs and Linear stay current because both receive the same approved source
    • The approved auth decision keeps rationale attached
      • Magic-link fallback ships first for mobile onboarding stability
      • Passkeys remain an ADR instead of disappearing into chat history
      • Acceptance criteria travel with the downstream Linear ticket
    • Private drafting and collective truth stay separate
      • Drafts remain private until someone promotes them for review
      • Approved context updates Documents and execution tools
      • Raw transcript stays background material, not shared knowledge by default

    Surface model

    • Four surfaces map the product boundary
      • Chat and Calendar serve the individual plane
      • Inbox and Documents serve the collective plane
    The problem

    Decisions decay between meetings, docs, and tickets.

    Meetings create intent. Docs flatten it. Tickets fragment it. By the time engineering starts building, the original why is usually stale, incomplete, or missing.

    Meeting

    Apr 17 · 35 min

    "Kill the password screen for new users — magic link first. Keep WebAuthn as fallback. Mobile is the priority."

    captured: rationale, trade-off, fallback

    Doc

    v3 · written next day

    "New onboarding will use magic links. WebAuthn may be added later. Mobile considerations TBD."

    lost: fallback rationale, mobile priority

    Linear

    FRB-431

    Implement password reset via magic link.

    lost: why, fallback, scope, owner

    Three surfaces, three different versions of the same decision. Nobody is wrong. Everyone is shipping from a different reality.

    AI proposes. The team approves.

    Freshbase is a review gate between conversation and execution. It pulls out decisions, requirements, open questions, and risks, then keeps the quote, rationale, and source attached until a human signs it off.

    CaptureInbox ReviewApproved SpecsAcceptance CriteriaADR TraceabilityLinear Handoff
    REC
    00:34:12
    S

    "We need to cut the password screen for new users — magic link first."

    R

    "I'm worried about email deliverability. We'd need a fallback."

    M

    "WebAuthn as fallback. Same flow, different rail. Mobile is the priority."

    Preparing Inbox proposals...
    magic-link-auth.feature

    Feature: Magic Link Authentication

    Scenario: User requests password reset via magic link

    Given the user has a registered account

    When they request a password reset

    Then a magic link is sent to their email

    And the link expires after 15 minutes

    Scenario: User completes reset via magic link

    Given the user clicks a valid magic link

    When they set a new password

    Then a confirmation screen is shown

    Not documents. Buildable artifacts with provenance.

    Each artifact links back to the conversation it came from and the decision that approved it. Edit one and the trace travels with the change.

    Approved specsUser journeysADRsAcceptance criteriaLinear handoffMCP Server
    BDD

    Behavior-driven specs

    Given-When-Then scenarios linked to the decision and conversation that produced them.

    UX

    User journeys

    User flows that preserve the rationale, constraints, and trade-offs behind each step.

    ADR

    Architecture decision records

    Technical decisions with context, consequence, source, and a reversible trail.

    AC

    Acceptance criteria

    What done means, attached to the approved decision before it reaches engineering.

    SYNC

    Linear handoff

    Tickets with rationale, acceptance criteria, and links back to the approving decision.

    MCP

    Contextualized development

    Approved specs flow to Cursor, Codex, and Claude Code through MCP, not screenshots.

    Built for teams that ship from approved context.

    rocket_launch

    Technical founders & CEOs

    Preserve intent clearly enough to build from it across time zones, contractors, and coding agents.

    explore

    Product Managers

    Stop chasing decisions across four tools. Approve criteria once; docs and tickets update from the same source.

    palette

    Product Designers

    Design from the rationale, not leftover bullet points. Journeys stay linked to approved decisions.

    architecture

    Tech Leads

    Keep ADRs, trade-offs, and prior constraints attached to the implementation path.

    terminal

    Engineers

    Build from approved context and hand it to Cursor, Codex, or Claude Code without private brainstorming leaking in.

    Half-formed thoughts should not become team knowledge by accident. freshbase separates private drafting from collective truth with an explicit approval gate.

    01

    Private by default

    Draft bases, rough notes, and half-formed plans stay personal until someone deliberately promotes them for review.

    02

    Collective by approval

    Approved decisions, specs, ADRs, and criteria join the team base with source, rationale, and ownership attached.

    03

    Trace travels with the work

    The source quotes, trade-offs, acceptance criteria, and downstream tickets stay linked after the meeting ends.

    04

    Linear keeps execution

    freshbase refines intent and routes approved context downstream. Linear remains the place where execution runs.

    Open beta now. Paid tiers when the product earns them.

    We are onboarding a small group of technical startups with 3-30 engineers that want approved specs before more execution noise.

    Founding teams
    Freeduring beta

    For teams willing to shape the review flow with us before Freshbase becomes generally available.

    • checkUnlimited Bases and team members during beta
    • checkInbox review for decisions, specs, ADRs, and criteria
    • checkLinear, GitHub, Notion, Slack, and MCP included
    • checkDirect Slack channel with the founders
    • check50% off the first paid year, locked in
    • checkNo credit card

    We'll reply within 48 hours with a calendar link.

    Future · enterprise
    Custom

    For organizations that need Freshbase deployed around stricter security, procurement, and data-boundary requirements.

    • addEverything in Founding Teams, plus:
    • checkSSO (SAML/OIDC) & SCIM provisioning
    • checkDPA, MSA, and audit support
    • checkDedicated tenant and BYO LLM option
    • checkData retention policies and audit logs
    • checkQuarterly business review with the founders

    Enterprise access opens after the beta cohort.

    lockSOC 2 Type II in progress
    credit_card_offNo credit card during beta
    event_availableCancel anytime

    Frequently asked questions.

    Can't find what you're looking for? Check our docs or reach out to us.

    No. Meetings are an intake surface. freshbase turns conversations into proposed decisions, specs, ADRs, and acceptance criteria, then routes them through Inbox before they become shared team context.

    Only approved Inbox items. Private drafts, rough thoughts, and raw meeting material stay separate until a human promotes them into the collective base.

    Approved specs, product decisions, ADRs, acceptance criteria, user journeys, and Linear handoffs. Each artifact keeps provenance back to the conversation and the approving decision.

    Linear remains the execution surface. freshbase sends approved context, rationale, criteria, and links downstream so tickets carry the why instead of replacing your delivery process.

    MCP gives tools like Cursor, Codex, and Claude Code access to approved product context, not private brainstorming or raw transcript sprawl.

    Founding teams get free access, direct founder support, and a tight feedback loop while we tune the approval flow, integrations, and product boundaries.

    The product is designed around private drafts, explicit approval, and enterprise controls. Team intent should stay yours, and model processing is scoped to generating outputs inside the service.

    Yes. Keep your meetings, planning calls, docs, and Linear workflow. freshbase adds the review gate between conversation and shared truth.

    Keep the why alive
    from conversation to commit.

    Freshbase turns product and engineering conversations into approved context your team can review, trust, and route into the tools where work actually ships.

    Early teams help define the approval layer before general availability.