0. How Monderun works
Promises can become invisible as a customer–supplier relationship develops. Weak monitoring can delay intervention, put recurring revenue under pressure, waste acquisition or recovery effort, and leave growth opportunities and trust behind.
Monderun connects the promise, the evidence and the next decision in one living record. These are possible business consequences, not proven losses or guaranteed benefits.
Promise → Agree → Measure → Substantiate → Signal → Compare → Decide → Assign & follow up → Review & grow
Available as demo · 30 fictional customers, three supplier examples; changes stay in this browser. The method concerns business value across sectors; software suppliers are the current examples.
Watch the introduction filmStart here
60 seconds: read 1 for the portfolio, 8 for the decision, 9 for responsibility and 10 for the result. You can start with management oversight even though the underlying work starts with an agreement.
Practical path: follow chapters 2–9 on one sample account, then return to the review in chapter 10. Nothing requires a long intake or a buyer login.
Examples follow the selected sector (Liquid Bulk / Dry Bulk) and one existing customer from the demonstration data, not a newly created account. Choose another sector to see other examples. Original customer and KPI names stay unchanged when you switch language.
1. Executive overview & portfolio
Home leads with observed improving outcomes, targets achieved, customers needing attention and open actions. Individual focus KPIs show their own baseline, current value and target, with sources on demand. More detail · Portfolio analysis keeps renewal bands, ARR, evidence, perspectives and the full customer table. Business overview remains a separate financial scenario, not customer savings.
Why it matters: Focus scarce management time on the accounts where weak proof and contract timing deserve a decision. An opportunity note is a reason to investigate, not booked expansion.
- Input
- The selected sample portfolio, recorded ARR, contract end dates, KPI evidence and existing actions.
- Output
- Distinct renewal groups with account counts, major-account concentration and clickable account priorities.
Do this next
- Choose a sample portfolio. Start with results and next actions; open More detail · Portfolio analysis for contracts and the full table.
- Read 0–12, 12–24 and 24–36 months as separate periods; inspect expired or beyond-36-month contracts when shown.
- Open an account needing attention, then inspect its evidence before choosing an intervention.
Practical example: Current view, Liquid Bulk / Dry Bulk: €1,985,000 ARR. The 0–12, 12–24 and 24–36 month periods contain 8 / 2 / 0 accounts and €1,600,000 / €385,000 / €0. These figures follow the selected sector and your saved edits.
ARR up for renewal is contract exposure, not confirmed churn or lost cash. Business overview’s probability-weighted loss and ARR-multiple valuation are scenarios, not a forecast or an assessed enterprise value.
Try it now
2. Add a customer and capture the business promise
Add customer creates a browser-local customer in the selected demo portfolio, with its own empty value agreement. Only the name is required. Industry is independent and optional, including your own industry. Objectives, measurements, rhythm and review remain optional in the same five steps. Customer drafts remain a separate idea list and never become portfolio accounts.
Why it matters: A checkable promise gives buyer and supplier a common question: what would count as success? The value record supports that conversation; it is not a signed legal contract or amendment.
- Input
- Required: customer name. Optional: industry (including Other / specify), demo portfolio, objectives, type, region, account owner, their department, separate measurement contact, ARR and contract dates; per outcome a starting point, target and unit (entered together), source and who measures; a first real reading; the review owner, team and due date.
- Output
- A customer, value agreement, measures and action saved in this browser. Anything left empty shows as Not provided and is not counted; the customer shows Setting up until it has a contract end date and a first reading.
Do this next
- Customers (main menu: Customers) lists every customer in one searchable list, your own first, whatever demo portfolio is chosen at the top; Overview has two views: Operational and Management view. Click Add customer and enter the name. Choose any industry or leave it empty. The optional Demo portfolio control selects where the account appears, not its industry. Save to create the customer.
- Write your own objectives or pick optional suggestions. We suggest starting with 3–5 key outcomes to keep focus. You can add as many as you need. None is also fine. Edit or remove your own objectives before saving; recorded KPIs remain unchanged. An objective becomes a measure only with a starting point and target.
- In step 4 choose how often you measure and where the number comes from: the source is saved with the measure, also without a reading. Add a reading only if you really have one; the screen shows the last saved reading and an identical reading (same date and value) is not added twice. In step 5 plan the first value review: saving again updates the same appointment, and each planned appointment has Edit and Delete (with confirmation). This is a planned appointment, not a review report. Finishing opens the customer page with “Customer setup complete” (or “setup finished” when optional steps stay open) and a short “What now?” list based on what is saved.
Practical example: The customer’s existing objectives concern faster vessel turnaround, less port waiting time and more vessel calls handled digitally. Start with an existing measure, not a new duplicate KPI.
Optional contact reuse: enter the account owner’s department and a separate measurement contact in Customer details. New measures suggest that measurement contact; existing reviewers, including empty fields, stay unchanged. New reviews/actions suggest the latest same-customer action by creation date (then ID), otherwise the account owner and department. Change or clear any suggestion before saving. Complete later keeps its existing first review when present. Edits apply only to the record you save, not to previous records or other customers.
Demo limitation: customers you add are stored only in this browser, are not a secure account and are not shared or synced. Use test names, not confidential details. No HubSpot, Notion, Fireflies or AFAS connection exists. You can change industry through Edit setup → Customer details. The demo portfolio stays fixed after creation. Industry explorer still contains only three starter packs, not a complete list of supported industries.
Value proposal is a separate editable fee and payer-split example, with a printable buyer offer; it is not a CRM pipeline or a saved customer contract. Industry explorer supplies starter ideas. Business model explores example subscription amounts, not payments.
Try it now
3. Agree what matters together
Shared value progress adds optional priorities to the same agreement and existing KPIs. It keeps joint attention focused without requiring a second review or buyer account.
Why it matters: We suggest starting with 3–5 key outcomes to keep focus. You can add as many as you need. Prioritisation is optional, not a limit. Record each side’s priorities instead of assuming that buyer and supplier want the same thing.
- Input
- One question: which outcomes will you discuss with the customer? Ticked = Key outcome, unticked = Monitor only. Whose priority, alignment status and sharing sit under optional advanced settings and are private by default.
- Output
- A focused internal preview of key outcomes prioritised by both sides, marked shareable and backed by explicit evidence-recipient permission.
Do this next
- Open the account agreement and find Shared value progress. Tick the outcomes you will discuss; the others keep their measurements as Monitor only.
- Optional, later: open the advanced settings to record whose priority it is or Proposed, Discussed or Agreed as a demo note.
- Inspect the internal preview. If evidence permission is absent, the outcome is withheld; shareability alone is insufficient.
Practical example: The customer already has measures for vessel turnaround, port waiting time and digitally handled vessel visits. Choose priorities only as an exercise; no buyer preferences or agreement have been supplied for you.
Proposed / Discussed / Agreed are entered demo notes, not buyer acknowledgement, legal sign-off or independent assessment. The preview is internal, not a public or secure buyer link; it leaves out internal commercial fields and private action details.
Try it now
4. Measure progress in context
Monitoring brings dated readings, measurement cadence and checkpoints together. The agreement shows baseline, current reading and target alongside the unit and source.
Why it matters: Regular, comparable observations reveal whether the intended outcome is moving. Activity or adoption can explain a conversation, but neither automatically proves business value or ROI.
- Input
- A dated value, consistent unit and measurement period, source, cadence and any known checkpoint.
- Output
- Updated measurements and progress, with missing or overdue checks visible.
Do this next
- Select the account and inspect the next measurement or overdue checkpoint.
- Record a reading in the agreement or measurement flow; keep its date and source.
- Interpret the actual value before target progress. A simulated monthly cycle creates labelled simulated observations, not a live sync or customer confirmation.
Practical example: For the customer, Turnaround time per vessel call starts at 210 min/vessel, is currently 175 and targets 160: 70% progress toward target. This is a process observation, not a monetary saving or proof of causality.
Progress above 100% means the target was exceeded; it does not make a percentage KPI exceed 100%. Released capacity is not cash, and overlapping effort or rework must not be counted twice.
Try it now
5. Substantiate each result
Evidence ledger follows a promise to its readings and sources; Proof passport keeps source independence, evidence maturity and value layer separate. A document reference can support a trace, but is not an audit by itself.
Why it matters: Knowing what supports a result makes management and buyer decisions more credible. Unknowns stay unknown; disagreement is a reason to reconcile sources, not silently choose a winning number.
- Input
- Observation, source type/system, date, recording party, original reference where present, and explicit evidence permissions.
- Output
- A traceable evidence chain and separate claims, with maturity and reconciliation indicators.
Do this next
- Check whether the KPI is an assumption, measured observation or customer-acknowledged example. In Passport, inspect the underlying evidence records as well.
- Follow the source/date and distinguish a manual reading, CSV import, documented trace and simulated reference. Records and documents contain example material; external context is not operational proof.
- When figures disagree, keep their records separate and inspect the reconciliation flag. Customer acknowledgement is not independent verification; verification requires a third-party assessment record.
Practical example: For the customer’s turnaround time per vessel call, open the claim and inspect who recorded the reading and when. Less waiting time does not prove avoided demurrage, and an estimated CO₂ figure stays an estimate.
Enter operational facts once in the original system. Source architecture groups CRM, ERP/finance, usage/support, documents/obligations, meetings, independent context and manual/CSV. Current references and simulations are examples, not connected third-party feeds or external audits. Meeting statements need human review, not automatic acceptance as savings.
Try it now
6. Review value with the right people
Value reviews put goals, observations and next steps into one conversation. Stakeholder value distinguishes the buyer, users, beneficiaries and cost bearer; Buyer assurance presents the permitted buyer-side view.
Why it matters: Buyer and supplier can recognise progress and unresolved questions without blame. The party that benefits need not be the party paying or taking action.
- Input
- Existing agreement and evidence, relevant stakeholder roles, explicit evidence recipients and optional check-in feedback.
- Output
- A review and buyer-safe brief, keeping internal commercial fields out of stakeholder information.
Do this next
- Open the account review and compare what was agreed with what is observed.
- Check beneficiaries and evidence recipients in Stakeholder value. A short Value Pulse adds feedback, not independent proof.
- Use the existing print review or Executive Value Assurance Brief. View permitted evidence without including internal ARR, margin or churn assumptions.
Practical example: At the customer, terminal planners, shipping agents and surveyors may benefit differently from the buyer. Ask which result matters to them; do not infer their roles or financial gains.
A demo perspective or role selector changes presentation, not secure access rights. Example acknowledgements remain example records; an opinion or entered alignment note is not a sign-off.
Try it now
7. Spot gaps before commercial pressure
Renewals & actions surfaces explainable signals from evidence, KPI progress, usage, review timing and contract dates. Read the triggered rule and actual date before treating an account as urgent.
Why it matters: Earlier attention can support revenue protection and trust. A failing relationship may affect ARR, time, recovery costs and growth; the signal does not prove a loss or predict churn.
- Input
- Existing readings and evidence gaps, recorded contract end dates and thresholds in Settings.
- Output
- An account attention list with reasons and links into evidence, decisions and existing actions.
Do this next
- Open a flagged account and read why it needs attention; a renewal 30 months away is not immediate loss.
- Inspect missing proof or stalled outcomes in the agreement or passport.
- Compare an intervention in Strategic decisions, or edit a recovery suggestion and add it as an ordinary action.
Practical example: Review the customer’s actual signal list rather than inventing an imminent renewal problem. Its recorded contract ends on 31 March 2027; what needs attention still depends on the current evidence and rules.
Signals are inspectable rules, not AI forecasts. Customer health opinions stay separate from measured value and do not feed the value exception calculation.
Try it now
8. Compare, then record the decision
Strategic decisions follows Identify → Compare → Decide → Follow up on the same account and evidence. Compare Monitor, Recover customer value, Prepare renewal early and Explore expansion side by side.
Why it matters: Make a choice financially interpretable under explicit assumptions, rather than presenting a modelled benefit as an achieved result.
- Input
- Account ARR plus your incremental retention/expansion percentages, contribution margin, annual and upfront intervention costs, horizon and benefit-start month; optional ARR multiple.
- Output
- Separate retained ARR, expansion ARR, costs and net contribution over the year/horizon, plus a separate valuation lens. A committed decision becomes an existing follow-up action.
Do this next
- Select the account and inspect its signals, contract date and evidence status.
- Enter only hypotheses you want to compare. Benefits start at the entered month; costs run over the full horizon. Missing inputs stay unestimated.
- Choose the option, then record department, person, deadline and next step. Commit it and open the linked action in Renewals & actions.
Practical example: For the customer, compare monitoring with recovering customer value around vessel-call handling. Leave retention and expansion blank until you have a defensible hypothesis; the handbook supplies no made-up effect, owner or intervention cost.
A retention percentage is an incremental scenario assumption, not a churn probability or guarantee. Supplier ARR, buyer benefit and net contribution are different quantities. Never add ARR-multiple valuation to cash or contribution; this is not artificial ROI.
Try it now
9. Make responsibility visible
The same action records appear in decision follow-up, Renewals & actions and the management summary. Department is separate from the named person, urgency and progress.
Why it matters: A decision becomes practical when someone knows the next step and its recorded deadline. Do not automatically assign value recovery to Customer Success.
- Input
- Explicit department, accountable person, next step, recorded due date, priority and state.
- Output
- A shared action you can edit and filter by department, progress or deadline.
Do this next
- New management decisions require a department; choose it yourself and enter the person, date and next step.
- In Renewals & actions, edit the same action and use the departmental or progress filter.
- Review overdue, next 7 days, next 30 days, no date assigned or completed. The 7-day and 30-day filters overlap; they are views, not totals to add.
Practical example: If you record a decision for a customer, the department and owner are only the ones you enter. Older actions can remain Unassigned, and no missing deadline is inferred.
Purple = Management & board; blue = Sales & commercial; teal = Customer Success; amber = Finance & operations; grey = Other or Unassigned. Department colours are not red/amber/green risk ratings.
Try it now
10. Review, learn and grow
Return from the action to the same agreement and review its next observation. The cycle is continuous: decisions change the next check, not the historical promise or evidence.
Why it matters: The dashboard protects visibility, evidence quality and accountable attention. It does not guarantee retention, growth, savings, trust, causality or enterprise valuation.
- Input
- The existing decision/action, next dated reading, customer feedback and any newly supported evidence.
- Output
- A better-grounded next review: continue, adjust the intervention, prepare renewal or investigate an opportunity.
Do this next
- Management/CEO checks concentration, evidence exceptions and choices; Sales checks whether promises and expansion ideas have support.
- Customer Success helps obtain the next observation when assigned; Finance checks costs, contribution and who actually receives a benefit.
- The customer reviews its priorities and permitted evidence with the supplier. Use Team views for emphasis, then return to the same shared records.
Practical example: The customer story ends with a clear next question, not an invented ROI: is the turnaround observation comparable across vessel types, does the buyer recognise it, and what should happen before the next review?
Customer value profile also keeps the signing priorities, current priorities, qualitative Total Business Value and manual health context distinct. A qualitative score is not currency; health does not replace KPI evidence.
Try it now
11. Glossary
- ARR
- Annual Recurring Revenue: the yearly subscription value of a contract. An ARR multiple estimates company value, not cash in the bank.
- Baseline
- The recorded starting value used to measure change; it may be unknown and need not relate to software.
- Target
- The agreed goal value. Progress above 100% means the target was exceeded — not that a percentage KPI exceeds 100%.
- Evidence maturity
- How well a claim is proven: commitment → customer evidence → cross-checked → verified (only with a third-party assessment).
- ROI
- Return on investment requires explicit benefit and cost evidence. Operational activity, target progress and hypothetical retained ARR are not measured ROI.
- Attribution
- How much of a change is caused by an intervention. Other factors can explain it; correlation alone is insufficient.
- Demurrage
- A contractual charge when a vessel waits beyond agreed time. Paid by the party the contract names; cannot be derived from waiting minutes.
- Customer acknowledgement
- The buyer acknowledges an observation. Useful, but not an independent audit.
- Renewal
- The moment a contract is extended — or lost. Evidence helps both sides make a better-informed decision.
- Source reconciliation
- When two sources disagree, both stay visible until people agree. Monderun never picks a winner automatically.
- Rules-based
- Signals use thresholds you can inspect and adjust in Settings; they are not predictions.
- Revenue exposure
- Recorded ARR attached to a renewal period or flagged account; not confirmed revenue loss.
- Business case
- What the improvement could deliver, as transparent estimates. Not measured results and not cash savings.
- Evidence (proof passport)
- What a result is based on: source, who recorded it and how strong it is. Example data is not verified.
- Results review (Value Review)
- The conversation with the customer about what has been achieved, with a written report. A planned review appointment is an action, not a report.
- ARR
- Annual recurring revenue: the yearly contract value. Unknown stays empty, not 0.
- Value agreement
- An editable record of objectives, measures and evidence, not a legal signature.
- Evidence provenance
- Where evidence came from, when, who recorded it and what permission and assessment support it.
- Independent verification
- A real independent third-party assessment with an assessor and supporting record. Example assessments are not certified verification.
- Contribution
- In the decision model: incremental ARR × entered margin, minus intervention costs; a scenario, not customer savings.
- Valuation
- A separate hypothetical ARR-multiple lens, never added to cash or contribution.
- Decision assumption
- A user-entered hypothesis about costs, timing or incremental retention/expansion, not an inferred effect.
- Action owner
- The explicitly recorded person accountable for the next step.
- Responsible team
- The explicitly selected function, separate from person, priority and risk; it can be unassigned.
- Shared value progress
- Optional priorities over existing KPIs with an internal permitted-evidence preview. Alignment notes are not buyer sign-off.
12. In development
These are future directions, not working controls or delivery commitments. The existing browser demo remains the current capability.
Authorised sources & independent assessment
Real third-party APIs, continuously sourced evidence and independent certified verification require authorised access, source reconciliation and assessor partnerships.
Secure collaboration & agreements
Monderun 2.1 access design is a read-only demo, not configured access or secure sharing. With real verified accounts, the dossier creator becomes administrator and can invite, set and revoke roles. Buyer access to vendor ARR, churn and margins stays denied; evidence needs explicit grants. Next gates: isolated organisations and verified users; scoped membership and revocation; private evidence storage; actor-bound decisions and audit; security review before any owner-approved production move. Secure accounts for the customers you add (today they live only in this browser), secure multi-tenant buyer access, enforced permissions, role-based login, real signed agreements and a production audit trail require secure accounts and reviewed access boundaries.
Monitoring & reviewed intelligence
Notifications, automated alerts and AI analysis or document/meeting extraction remain future work. Extracted statements must be proposed observations with human review, original date/source and consent—not automatic acknowledgement or savings.
Advanced decisions, reporting & language
Advanced forecasts, portfolio optimisation, expanded reports/exports and complete product-wide localisation are separate work. Existing print and CSV controls remain available; deeper expert/chart/narrative translations are incomplete.