Record the conversation · Keep the intelligence · Grow the relationship

Product

A briefing after every meeting, and a brain for every client.

Routenna listens the way a seasoned colleague would, using the practice pack you chose, and hands you the things that create work. Each one arrives with the moment it was said, so you can hear it before you act on it.

CLIENT REVIEWRECANNOUNCED BY NAMESTOPPABLE BY ANYONESTOP
Capture, from calendar rule to a self-identifying bot to a stop control anyone in the meeting can reach.

One engine. The pack decides what it listens for.

Practice packs

A renewal conversation and a safety walk-through are different meetings. A pack supplies the themes, the meeting modes and the brief templates; everything else in the product: capture, review, isolation, consent, deletion: is identical. You pick a pack in onboarding and change it whenever you like.

  • General Advisory

    At launch

    Consultants, fractional executives, anyone advising a business

    Owner dependency, growth constraints, expansion events, margin pressure, hiring, succession.

    • Discovery
    • Client Review
    • Working Session
    • Strategy Session
    • Check-in
  • Insurance & Benefits

    At launch

    Benefits and insurance brokers

    Renewal cycles, plan design, employee education, claims coordination, census changes, competitive pressure.

    • Renewal Review
    • Client Review
    • Prospect Discovery
    • Service Issue
    • Enrollment
  • HR & Risk

    At launch

    HR and safety consultants, PEO service teams

    Documentation discipline, terminations, employee-relations incidents, hazard observations, training gaps, classification questions.

    • HR Consultation
    • Risk or Safety Visit
    • Investigation
    • Training Review
  • Operations

    At launch

    Owners and operators, on their own team's meetings

    Decisions, owners, blockers, and the constraint that keeps coming back.

    • Team Meeting
    • 1:1
    • Vendor or Supplier
    • Customer Call
    • Planning Session
  • Client Services · Financial Advisory · Coaching

    Fast follow

    Agencies, accountants and bookkeepers, coaches

    Scope and approvals, document requests and planning threads, goals and obstacles.

    • Kickoff
    • Creative Review
    • Planning Session
    • Session
    • Progress Review

Seven kinds of finding, each with its receipt.

Every finding carries three things: the transcript timestamp that proves it, a confidence score, and a label: fact, inference or recommendation, so you always know whether you are reading evidence or judgment.

Below the confidence threshold, a finding is filed as “possible” — never dropped, never asserted.

  • Commitment

    who owes what to whom, and by when

  • Decision

    what was decided, so it is never re-litigated from memory

  • Concern

    what the client is worried about, before it becomes churn

  • Signal

    an early indicator tied to a named theme in your practice

  • Opportunity

    a service need surfacing in the client's own words

  • Risk flag

    exposure your professionals should look at: flagged, never advised

  • Fact update

    a change in the client's world worth recording

  • And nothing else

    A closed vocabulary is the point. Findings your team cannot name are findings your team cannot review.

00:14:32COMMITMENT0.86CONCERN0.74SIGNAL0.61

Extraction, with the evidence attached

Speech becomes timestamped chunks; findings are lifted from them and keep a pointer back. Model output is validated against a strict schema before it can touch the database: malformed output is rejected and retried, then quarantined, never written half-way.

PROPOSED FINDINGMAR 04: CLIENT REVIEW2 open commitmentsAPR 09: WORKING SESSION3 open commitmentsMAY 12: CLIENT REVIEW1 open commitmentRAISED 3x

Review before it counts

After each meeting you get a review queue. Accept a finding and it joins the client record. Edit it first if the wording is off. Dismiss it and the dismissal is logged. The client timeline shows what your people confirmed.

A second opinion

Three advisors read the meeting. They do not always agree.

Everything else here answers what was said. This answers what it means and what to do — from an HR read, a risk read and a business read, run separately over the same transcript.

They disagree on purpose. A people question and an exposure question are not answered by the same instinct, and the same sentence is often both.

Every piece of advice cites the moment it came from, and is labelled fact, inference or recommendation. An advisor with nothing to say returns nothing rather than restating the meeting. You choose which of them run.

One moment in the transcript

“We’ll just move Dana onto the second crew’s timesheet for now.”

00:22:41operations manager

  • HRTwo crews on two timekeeping systems means two rounding rules. Worth checking which one Dana is paid under before this becomes the precedent.RecommendationThis week
  • RiskIf the second crew’s hours feed a different comp classification, a claim would be filed against the wrong one.InferenceBefore month end
  • BusinessNothing to add. The staffing decision itself is sound.Fact

Synthetic example. An advisor with nothing useful to say says nothing, which is why the third line is empty of advice rather than padded with some.

Ask meeting · Ask client

Questions answered from one client’s meetings, and no one else’s.

Ask what is still open, what they were worried about last quarter, what you recommended and whether they acted. The retrieval is scoped by organization and client in the database, and a dedicated leakage test seeds two clients with distinctive facts and proves the answers never cross.

Answers carry the same timestamps and the same fact / inference / recommendation labels as everything else.

Ask this client

What have we promised them that is still open?

Two commitments are outstanding: the handbook draft, promised before the renewal meeting, and a follow-up on the second-shift staffing question.

  • 00:14:32consultantFact
  • 00:38:07client operations managerInference

Scoped to one org_id and one client_id in the database. Synthetic example.

The client brain

Findings accumulate. That is the whole product.

Per client: the meeting history, open commitments, unresolved concerns, and recurrence detection that notices when a theme has come up in consecutive meetings. When a colleague covers your account, they open the client and already know what was promised and what is still worrying them.

Exports carry accepted findings only, and every exported assertion is as traceable as an on-screen one. how that is enforced.

Concern

Proposed · awaiting review

“Third time we’ve raised the second-shift coverage gap. It keeps getting deferred.”
00:38:07client operations managerconfidence 0.77Inference

Synthetic example. No client data appears anywhere on this site.

A meeting is the input. This is what you do with it.

In the product

Capture and extraction are the first half. The rest is the working week: what you owe, what keeps coming back, what to read in the corridor before you walk in, and where the accepted work goes next.

  • Prep

    The two minutes before you walk in. What you already know about this client, what is still owed, and what they raised last time — rather than opening the timeline and reading it yourself.

  • Intelligence brief

    The meeting as a document you can send: numbered recommendations, the evidence under each, print-friendly. Confirmed content only, so nothing a person has not accepted can appear in something that leaves the building.

  • Tasks

    Every commitment lifted out of the meeting it was made in, so answering “what do I owe” does not mean opening each meeting and reading every finding.

  • Insights

    The one place that crosses the meeting boundary. A theme raised once is a remark; the third time it is a pattern, and this is where that becomes visible.

  • Reports

    Open commitments grouped by client, meeting volume over time, recurring themes. On screen, as CSV, or printed. No composite scores and no projections past the last real month.

  • Notes and templates

    Type during the meeting; what you meant to cover survives into the recording and is read by the advisors. Templates start that list from something other than a blank page.

  • Browser recorder

    For the meetings that happen in a room rather than on a platform. It lands in the same pipeline as everything else, so retention, transcription and extraction do not care where the audio came from.

  • Slack, HubSpot and webhooks

    Where accepted work goes next. Only what a person confirmed is ever pushed, requests to your systems are signed, and the destination address is checked before anything is sent.

  • Yours, on a shared account

    A team account does not mean every meeting is the team's. Your captures stay yours unless the client is shared or you share the meeting, and your review queue only ever shows your own.

Everything above reads the same confirmed record. Nothing here shows a finding a person has not accepted, which is why a brief can be sent to a client and a report can be handed to a partner.