Back to portfolio

Concept · Maybern · comments & notifications

Who for

Fund accountants and controllers who have to explain a number that has since changed.

The problem

A question asked about a figure does not survive the figure being restated.

Why now

Agents are now in the seat that moves the numbers, which turns who asked, who approved, and against which version into a design problem rather than a database one.

Why me

I have shipped a system that pins the scoring rubric version to every record, so a score can still be explained six months after it was produced.

User story

As a fund controller, I need my question about a figure to stay attached to that figure when it is restated, so that I learn the answer changed instead of finding out from an LP.

Success

Every restatement reaches the people who asked about the old number before it reaches an investor — and the close does not get slower.

You already drew this problem.

Sven Manzanarez, applying for Product Designer (Senior, Lead). Every figure on this page is invented.14

Question“We need to better track accrued expenses here.”
Question“Can I see the effect of the fee break and offsets?”
Question“Why doesn’t Invested Capital tie out to the GL?”
Question“Do projected management fees reflect the recent sales?”
Control“Please get Dave’s signoff after updates”

From the illustration on maybern.com/solutions/fund-intelligence.2

What I read, and what I inferred

No access to your users, so this is inference. Break it wherever it is wrong.1

Your illustration puts questions and a signoff on the artefacts. → Discussion belongs on the number.
Notes (Optional) sits at event level and per row. → The location is already settled.
Rows badge 1 Reallocation Event. An agent writes results back. → Figures change after the fact — often not by a person.
The squad owns visualizations, tasks, notifications and commenting. → It is one problem, not two.

What you already have

Three things already on your screens.

A place for words, already sited

Writing already sits beside a figure at two levels — the event, and the single row.

Restatement, already modelled

Rows badge 1 Reallocation Event — amendment is already first-class.

Maker / checker, already named

Draft → Finalize Event, with Notice Status gating what reaches investors.

Five principles

Written before the screens. Where two conflict, the lower number wins.

Anchor to the object, surface on the symptom.

Attach the thread to the object that computed the figure. Show it everywhere that object feeds.

A machine can propose. A person disposes.

Agents compute restatements. A named human finalizes them, and the maker is never the checker.

Record everything. Announce selectively.

Two different decisions. Collapse them and you get alert fatigue and missing history.

Never resolve a question on the author's behalf.

A moved figure gives a comment context, never closure. The system does not decide the asking is over.

Use the words already on the screen.

Every state here maps to one you already ship. A second vocabulary is a second thing to learn.

One figure, one thread, one restatement

Four steps. Drive it.

Buttons here are not part of the proposal. Everything inside the frame is.

◷   ?   ⚙
Maybern Fund II
Fund Phase
Commitment Period
Last Close Date
8/11/22
  • Commitments
  • Capital Activity
  • Performance
  • Fees
  • Investments
  • Credit Facility
  • Configuration ⌃
‹ Fund Intelligence

Performance

Finalized
Net IRR
15.1%
Net of fees and carry
TVPI
1.71×
Value / paid-in
DPI
0.84×
Cash on cash
Unfunded
$147.7M
Available capital
Fund-level measures Fund›Investor Class›Investor Entity ⤓ ⌕ ▥ ⤢
MeasureValueAs ofBasisRevisionThread
Gross IRR22.4%30 Jun 2026LPA cl. 7.14
Net IRR15.1%30 Jun 2026LPA cl. 7.34
TVPI1.71×30 Jun 2026LPA cl. 7.44
DPI0.84×30 Jun 2026LPA cl. 7.44
Unfunded commitment$147.7M30 Jun 2026Sched. A4
Net IRR 2 comments
Reply…

How you get here

No Comments destination, and there should not be — a thread reached from a list arrives stripped of the figure it is about.

Swipe the diagram sideways →

PRIMARY ROUTE MEASURE THREAD Gross IRR + Net IRR 2 TVPI + click the count Thread · Net IRR 2 COMMENTS scoped to the measure you arrived from SECONDARY History control ◷ index of threads waiting on you Notification deep-links to the anchor, not the page open the same thread REJECTED Inline marker beside the label fights the label for scanning Hover-only affordance hides the count that makes the column worth having Promoting Notes (Optional) puts the record behind an edit mode
One thread, three doors. The count is the only control — empty rows show the same one, faint. Reading a thread and starting one are the same gesture.

It costs a column in a table that already scrolls sideways. Under 620px the count moves inline beside the label — the rejected option wins at the width where its objection stops applying.

Every comment attaches to a revision, not to the figure. So when the value moves, the thread does not quietly go wrong.

Where this lives

Your objects split in two:

  • Transactional objects — Capital Event, distribution, fee posting. Identity, lifecycle, a Notes field.
  • Derived measures — Net IRR, TVPI, DPI, NAV. None of that. They are computed.

A question on Net IRR is never about Net IRR. It is about the mark that moved it, asked where the symptom is visible — principle 1.

Swipe the diagram sideways →

Maybern UI Claude · Slack via Maybern MCP posts to posts to TRANSACTIONAL OBJECT Capital Event 4412 Harbourline Q3 mark · Draft THREAD · 3 unanswered mention blocks Finalize computed into Net IRR thread surfaces TVPI thread surfaces DPI thread surfaces NAV thread surfaces DERIVED MEASURES a question asked here resolves to the object that moved it One store, several front doors. The measure is where the symptom is visible; the object is where the conversation belongs.
The green dashed path does the work. Without it a comment is orphaned the moment anything upstream changes.

On Slack. You do not win by asking people to leave it — you make it a client. Your MCP already reads and writes Maybern, so a reply from Claude lands on the object.

This split is read off your screens, not your schema.3

How we would know it worked

Success = restatements that reached every open thread before the investor notice all restatements on a figure that had an open thread target 100%
Gate Median time to finalize does not rise. Governance that slows the close has failed, whatever the ratio says.

Everything else I would instrument — adoption, reply time, dismiss rate per measure — exists to move that one ratio or defend that one gate.

What I would need to ask you

Fund accounting is not my domain. Five questions that would change this:

  1. Who actually comments today? A thread the administrator can read is a different object from an internal one.
  2. Does a restatement have a type users distinguish? Error corrections probably behave differently from valuation updates.
  3. How often does a noticed figure move again? That decides whether “always announce” is an exception or the norm.
  4. Is materiality already in your customers’ own documents? Then the product should read it, not invent it.
  5. Does a comment ever need to reach the audit record, or is it deliberately kept out?

If this is useful

A lead-qualification platform in production, where the rubric version is pinned to each record at capture — so a score can still be explained six months on. Same problem, smaller stakes.

Five years of design ownership, production front-end in Next.js and TypeScript. This page is working code, not a picture of one.

Annotations

  1. Sources. I have not used Maybern. Built from your solutions pages, marketing screenshots, engineering post and MCP docs. I am an applicant, not a customer. ↩
  2. The five notes. Verbatim from the illustration on maybern.com/solutions/fund-intelligence. Marketing artwork by your team — not customer quotes. ↩
  3. The transactional / derived split. Read off your screens, not your schema. If a derived measure is already first-class internally, the anchoring gets simpler than I have drawn. ↩
  4. The prototype. Fund II, its figures, Harbourline Logistics and everyone in the thread are invented. ↩
  5. Not affiliated with Maybern. An unsolicited concept for a job application. The shell is redrawn from marketing screenshots — not their code, files, or endorsement. ↩