One meeting, drawn. Then every meeting.

Riffmap draws one call in full — then what six weeks of calls add up to. Every picture below is Riffmap’s own page on demo data.

Eight weeks on a strip, a bar per meeting from Aug 31 to today — the portal’s own window strip
Wed Sep 16 · the roadmap offsiteone meeting, drawn

One meeting, drawn

Fifty-five minutes, and where every one of them went.

A roadmap offsite at Lumen Robotics, an invented company, the way Riffmap gives it back.

The topic timeline of the offsite: small talk and a status update in grey and blue, three brainstorm bursts in orange, discussion in green
Kind of talk, minute by minute.
The four numbers: 55 minutes, 51% was brainstorming, 32 ideas captured, 9 decisions marked, 10 actions
The whole call in four numbers.
The clock: topics on the outer ring, kind of talk on the inner, 55 minutes, 4 on the call; the agenda beside it with minutes per topic
Where the minutes went, by topic.
Who was on the call: four discs, each ring that person’s share of the talking — Tomasz 29%, Rosa 28%, Maya 25%, David 18%
Who said how much.
Where the time went and what came out of it: four speakers flow into five topics, which flow into nine outcomes; small talk marked as no outcome by design
Who talked about what, and what each topic produced. Pans sideways on a phone.
The first board, Robot health monitoring: three lanes, Sensor drift, Alerting and Dashboard; stickies from David, Maya and Rosa; a decision badged; a lineage line into the Alerting lane
The brainstorm map — lanes by theme, decisions badged, who said it on every sticky. Pans sideways on a phone.
Demo · replay of a finished call
The replay — the ideas as a graph, in the order they were said. Pans sideways on a phone.
A decision sticky: Pull the lidar calibration drift curve into a shared store this quarter — Rosa, 12:25
Rosa, at 12:25 — verbatim from the transcript
“Decision: we pull the lidar calibration drift curve into a shared store this quarter, not just leave it buried in per-robot logs.”
Nothing invented — click a sticky and read the words it came from, checked against the transcript in code.

A demo: Lumen Robotics’ roadmap offsite, Sep 16, four people, drawn by Riffmap.Open this map →Ask for an invitation →

A sales call

The agenda you planned, against the call you had.

A sales call gets its own page.

The agenda as a ruler: seven rungs, Rapport, Agenda, Discovery, Demo, QA, Commercials, Next steps, each topic a band on the call’s clock
The agenda, expected and actual. The rungs with no band never happened. Pans sideways on a phone.
Who held the floor: seller above the line, buyer below, band height is seconds spoken — 45% buyer talk, 18 of 40 min
Who held the floor — 45% buyer talk. Pans sideways on a phone.
What the buyer asked: one row per category, one mark per question — four answered, one commercial question deferred
What the buyer asked, and whether it landed.
The moment the buyer leaned in: one line per buyer, an up-tick on the dashboard at 5:20, a down-tick on price at 25:06
The moment the buyer leaned in — Marcus lit up on the dashboard at 5:20 and pushed back on price at 25:06.
Buyer, question, outcome: Lena and Marcus flow into five question categories, which flow into answered, deferred and a reaction
From buyer to question to outcome. Pans sideways on a phone.

A demo: Lumen Robotics’ dashboard demo to Okapi Cold Chain, Sep 22, 40 minutes, two buyers.Open this map →

An interview

Every question the panel asked, and how long the answer ran.

An interview gets the question ladder.

The interview template as a ruler: Rapport, Background, Role, Candidate QA, Next steps
The interview’s own template as the ruler. Pans sideways on a phone.
Who held the floor: interviewer above the line, candidate below — 57% candidate talk
Who held the floor — 57% candidate talk. Pans sideways on a phone.
The question ladder: four interviewer questions, Cartwheel ownership, Reason for leaving, Debugging approach, Proudest project, each with the answer’s length marked
The question ladder — one rung per question, and how long each answer ran.
What the candidate asked: three questions, Team, Product and Process, all answered
What the candidate asked back.

A demo: Lumen Robotics’ panel interview for a senior backend engineer, Oct 5, 39 minutes.Open this map →Ask for an invitation →

Your meetings, lately

Six weeks of one team, on one screen.

Eleven meetings at Lumen Robotics, Aug 31 to Oct 8, and what they add up to.

Eight weeks on a strip, a bar per meeting from Aug 31 to today
Eight weeks, a bar per meeting.
Eleven meetings, 7.1 hours of talk, 14% was brainstorming, 54 ideas captured, 8 decisions marked, 28 outcomes
Everything the eleven maps add up to.
The topics treemap: seventeen topics sized by talk time, Robot health monitoring 89 min the largest, a wave mark on the seven that came back
Topics by talk time — the wave mark on the seven that came back.
Time by mode: a radar with four axes — Discussion 54%, Reporting 20%, Brainstorm 19%, Small talk 7%
Time by kind of talk — the team’s signature.
Sales calls: three bars, one per call with Okapi Cold Chain, the buyer’s share as the split, questions under, reactions above, the next-step cap
Every sales call as one bar — the buyer’s share, questions, reactions, the next step.
Interviews: one bar, the candidate’s share 57%, the interviewer’s questions under it
And the interview the same way.

A demo: the same invented company’s six weeks, on Riffmap’s own overview.Open the eleven maps these are drawn from →

Topics that keep coming back

Seven topics came back. Each one is a river.

A topic that comes back in a second meeting earns a river.

Seven rivers on one calendar: Okapi Cold Chain pilot, Backend hiring, Next steps, Rapport, Fleet Intelligence pricing, Robot health monitoring, Q&A — a bar per meeting as tall as the minutes on the topic
A lane per topic, a bar per meeting as tall as the minutes it got. Two have gone quiet.
One river, Fleet Intelligence pricing, across four meetings: sub-threads Per-robot vs per-site, Tiers and Annual discount leave the bank into their decisions; three actions still open; Copy as agenda
One topic, four meetings. What got decided leaves the bank; what is still open rides to today — with Copy as agenda.

A demo: Lumen Robotics’ topics over six weeks, on Riffmap’s own pages.Open the eleven maps these are drawn from →

See your own calls this way.

Invite-only while Riffmap is small. Tell us which notetaker you use.

One private portal per team, Google sign-in. Riffmap never joins or records a call.