bloomintelligence
Built in Switzerland

The documentation
your company never
had time to write.

Built and maintained from your existing tools. Cited to source. Queryable in plain language.

The problem

Decisions live in heads. Client context lives in scattered Slack threads. Product reasoning lives in old meetings.

Companies know they should write it down. Nobody has the time. Wikis go stale. AI tools hallucinate because they have no real context.

What’s documented

Everything a new hire
or AI tool would need
to understand the business.

  • Clients, status, history, commitments.
  • Products, decisions, and the reasoning behind them.
  • Operations and the playbooks usually trapped in heads.
  • People, roles, and who owns what.
  • History: what happened, when, and why.
Clients/Kvitfjell Ski AS
Active

CHF 4.8K MRR · 14 mo tenure · Health: Strong

Renewal in 87 days · Last touch 2d ago

About

Norwegian alpine resort, B2B reseller of our portal for season-pass sales. Anna Berg (Head of Ops) is primary. Tech contact is Jon Kvist (CTO). We custom-built the partner logo bar for them. They pay enterprise tier for the integration support, not seat count.

Open commitments

4 open
  • Ship partner logo barby Dec 1
  • Send updated SLA doc2d overdue
  • Integration spec reviewdue tomorrow

Key decisions

  • Postgres over Firebase for analytics backend

    Analytics needs SQL joins across 50M rows.

  • Pricing held at CHF 4.8K

    Held via scope cut, not a paid discount.

People

  • AB

    Anna Berg · Head of Ops

    Primary
  • JK

    Jon Kvist · CTO

Fed by your tools

Maintained as your
company runs.

Connected to Slack, calendar, meetings, CRM, Linear, and docs. Every fact sourced. Every conflict flagged.

  • Pulls from the tools your team already uses.
  • Extracts decisions, commitments, releases.
  • Sources every fact, links every claim.
  • Flags conflicts when sources disagree.
Connected sources
Syncing

Fed continuously

Slack

12 channels · live

Calendar

Meetings · transcribed

CRM

Hubspot · 14 clients

Linear

146 issues · 4 projects

Email

Threads · client-tagged

Docs

Notion + Drive

Extracted this week

  • Decisions47
  • Commitments23
  • Client facts412
  • Conflicts flagged6

Every fact sourced. Every claim linked. Conflicts flagged when two sources disagree.

How teams use it

Read it. Query it.
Build on it.

Read it

New hires read it on day one. Senior people stop being the bottleneck for context.

Query it

Anyone on the team can ask in plain language. Answers come back cited to source.

Build on it

Studio and workflows run on the same foundation. Every new app gets it for free.

Grounded, not generated

Every fact points back
to where it came from.

bloom extracts typed facts from real sources, scores its confidence, and refuses to answer beyond what it actually knows.

  • Structured extraction with strict schemas.
  • Source attribution on every fact.
  • Confidence levels on every claim.
  • Conflicts flagged, not auto-resolved.
Brief me on Kvitfjell before 3pm· 5 sources cited
Grounded
Brief me on Kvitfjell before my 3pm call.

Current state

Active client, CHF 4.8K/mo, tenure 14 months. Confirmed Dec 15 go-live for the new partner portal.[1]Health strong; 89% weekly active usage.[3]

Open commitments

  • Overdue · SLA doc to Anna (Lena, 2d).[2]
  • Partner logo bar, Dec 1 (Marco).[1]
  • Integration spec review tomorrow (Sofia).[4]

People on their side

Anna Berg (Ops · primary), Jon Kvist (CTO), Siri Moen (Support).[3]

What’s the SLA doc status?

Drafted Mar 4 by Lena, blocked on legal review.[2]Anna pinged twice (last yesterday, 09:15).[5]Recommend acknowledging today and committing to a Friday turnaround.

Draft a reply to Anna.

Sources · cited inline

5 · varied types
  • [1]
    MEETING

    Mon standup

    9:02 · Marco

  • [2]
    EMAIL

    SLA renewal thread

    Anna Berg · Mar 4

  • [3]
    DOC

    Client page · auto-maintained

    synced today

  • [4]
    LINEAR

    KVT-412 · cache invalidation

    Sofia · yesterday

  • [5]
    SLACK

    #kvitfjell · 9:15

    Sofia · today

Draft a reply to Anna
Why not just use…

Notion is a tool for writing documentation.

bloom builds the documentation.

Glean searches your existing docs.

bloom structures what’s worth searching.

ChatGPT answers from general knowledge.

bloom answers from yours, with citations.

Internal wikis go stale within months.

bloom stays current as your company changes.

How it works

Four to six weeks to the first version.
Continuous from there.

Weeks 1–2

Integrate

Connect your tools. Set scope and schemas. Initial extraction begins.

Weeks 3–6

Build the first version

Documentation populated, reviewed with your team. Confidence dialled in.

After

Run it with your team

bloom maintains the foundation continuously. Code stays yours.

Built for teams whose
knowledge has outgrown
the people holding it.