Alturian internal · Operating plan v0.1

Monkeybar — from a website to an operating business.

A hand-off document. Anyone in Alturian should be able to pick this up and run with it — what to build, who builds it, in what order, and how we know it's working.

Audience
Whoever Alturian appoints to lead Monkeybar — plus anyone supporting from central
Status
Working draft · everything in here is a proposal, not a verdict
Companion
monkeybardigital.com · the public narrative this plan operationalises
Executive summary · the ask

Monkeybar is an Alturian-owned digital transformation consultancy for Jakarta SMBs. The narrative and website exist; the operating chassis does not. This plan specifies what to build, who builds it, in what order, and at what cost.

What we need from leadership
  • Appoint a Lead — gating item; nothing starts without it
  • Confirm F&B / Real Estate as the lead vertical pair (or swap)
  • Greenlight Day 1 — plan assumes start within 4 weeks of approval
What success looks like
  • Day 90: 1 Build live · 1 Improve retainer signed · 3-person pod · 2 case studies published
  • Month 6: break-even on cumulative cash
  • Q4 exit run-rate: ~Rp 3.6 B / yr · ~58–65% contribution margin
Open questions to close
  • Lead candidate — identified, or sourcing to start?
  • F&B + RE as the lead vertical pair, or swap?
  • Year 1 capital — working-capital floor is Rp 200–250 jt (Months 1–5 dip). Does Alturian want headroom on top for marketing or contingency?
  • Internal customer #1 — any Alturian portfolio biz to seed the first case study?

Full open-question context lives at the end of section 7 (First 90 Days). The plan below is structured for a ~20-minute first read; use the table of contents to drill into any section.

  1. Where Monkeybar is todaystarting point + value chain
  2. Offer & ICPi — what we sell, to whom
  3. Demand Generationii — how leads enter the pipeline
  4. Delivery Engineiii — sprints, verticals, stack
  5. Team & Orgiv — pod, hiring sequence
  6. Operating Cadence & Metricsv — rituals, KPIs, P&L
  7. First 90 Daysvi — week-by-week
  8. Templates & playbooksappendices A1–A6
  9. Glossaryjargon, decoded
01 — Starting point

What we have, and what's missing

Monkeybar's narrative is solid. The execution chassis underneath it isn't built yet — that's what this plan is for.

What we have (the narrative)
  • A productized point of view — "your team isn't the problem; the system they're working around is." Digital transformation for SMEs that already have tools, not greenfield rebuilds. audit existing stack · design integrations · stay engaged through adoption — explicitly not a ripout-and-replace pitch
  • A three-phase methodology — Review → Build → Improve. Branded, repeatable, easy to sell. Review = audit + plan + estimate · Build = 2-week sprints + integrations + handover · Improve = monitoring + iteration
  • Six target verticals — F&B, Retail/E-commerce, Professional Services, Real Estate, Healthcare, Finance/Advisory. stated on the website — but six is too many to lead with; we'll narrow this
  • A free diagnostic offer — 30-min conversation, no obligation. Naturally qualifies and disarms gatekeepers. already a public CTA on the site · works as a top-of-funnel mechanism
  • Concrete impact claims — 4–6 hrs/wk saved, +40% leads captured, 80% reporting-time reduction, ~3-month ROI. good enough to use in pitch decks · need 2 case studies to back them up by Day 90
What's missing (the chassis)
  • No named owner — there is no Monkeybar lead. Without one, no one is accountable for the metrics in this plan. first hire / appointment of the entire plan · everything else is downstream of this
  • No defined ICP within the verticals — "F&B" and "Real Estate" are categories, not customers. We don't know what size, what stage, what willingness-to-pay. a 3-branch café and a 50-restaurant chain need entirely different builds — we have to pick
  • No pricing — every quote starts from zero. No anchor, no signal, slow sales cycles. competitors with public price ranges close 2–3× faster on small projects
  • No demand-gen engine — the diagnostic CTA exists, but nothing is feeding it. no outbound rhythm, no content cadence, no partner channel
  • No delivery playbook — "two-week sprints" is a phrase, not a recipe. What's in Sprint 0 vs Sprint 3? Who's in the room? What's the QA bar?
  • No P&L target, no operating cadence, no case studies — we don't know what good looks like, when we'd review it, or what we'd point to.
02 — Value chain

How Monkeybar makes money

A four-product ladder. Diagnostic and Review exist to qualify into the prize, which is the recurring Improve retainer. Everything in this plan is designed to maximise the rate at which prospects climb that ladder.

The ladder, in order
Top of funnel — free, qualifies in
Stage 01AudienceOutbound, content, partner, referral
Stage 02Diagnostic30 min · free · structured
Prospect pays
Paid ladder — the commercial chain
Stage 03Review2 wks · fixed fee · audit + plan
Stage 04Build6–10 wks · fixed fee · integrate & train
Stage 05ImproveMonthly retainer · the prize
Stage 06ExpandNew use case, new branch, referral
North-star metric Annualised retainer revenue from Improve
Why this is the prize Predictable, defensible, compounds with case studies — and is what makes Monkeybar a business rather than a project shop
What kills it Building one-off projects with no Improve attached · accepting Build SOWs that don't include adoption metrics
i — Offer & ICP

What we sell, and to whom

Owner Monkeybar Lead
When it's due Locked by end of Week 2 · revisited at the 90-day review · re-opened only if win-rate drops below 20%
How we'll know it works ≥50% of diagnostics convert to a (creditable) Review within 14 days; ≥70% of Reviews convert to Build inside the 30-day credit window
The four-product ladder
  • 1. Diagnostic — 30 min, free, structured. A scored conversation, not a sales call. Output is a one-page "fit memo" sent within 24h. 10 standard questions · 0–100 fit score · auto-disqualifies if score < 40 — saves both sides time
  • 2. Review — 2 weeks, fixed fee, creditable against Build. Process audit, gap analysis, prioritised plan, fixed-fee Build estimate. Framed as a refundable deposit, not a "free proposal" or a separate sale. deliverable: 12–18 page Review pack + a 60-min readout · fee credits 100% to Build if signed within 30 days · keep-fee otherwise
  • 3. Build — 6–10 weeks, fixed fee. Sprint 0 (re-confirm scope) + 3 build sprints + handover sprint. Always includes a 30-day adoption check. we walk away on day 60–70 with the system live and the team using it — not "deployed and we're gone"
  • 4. Improve — monthly retainer. Performance monitoring, monthly adoption review, iteration backlog, quarterly strategy session. Auto-renews; signed on Build kickoff, not after. bundling Improve into the Build SOW lifts attach rate from ~30% (sold after) to ~70% (sold inside)
ICP — narrow to two verticals to start
  • Lead with F&B (multi-branch) and Real Estate (brokerages, 5–25 agents). Both are operationally complex enough to feel the pain, big enough to pay, small enough to decide quickly. F&B sweet spot: 3–15 outlets, Rp 5–50B revenue · Real Estate sweet spot: established brokerage with 5–25 agents and no proper CRM
  • Geography: Jakarta first — that's where Alturian already has presence and warm references. Greater Jakarta only after 3 wins in-city; rest of Indonesia after 10. Cross-border is a Year 2+ conversation.
  • Buyer: Operations Director, Head of Ops, or owner-operator. Not the CTO (we're not a tech vendor) and not Marketing (we're not an agency).
  • Disqualifier: "We need someone to build us a custom platform." That's a software-house pitch. Our pitch is "we make the tools you already have actually work together."
  • Why not the other four verticals yet: Retail/E-com is over-served by Shopify ecosystems; Professional Services and Healthcare have longer cycles; Finance has compliance overhead we'd need 6+ months to absorb. Park them for Year 2.
i — Offer & ICP (cont'd)

The price ladder

Priced for the Jakarta SMB owner-operator. The mental model: Review is a comfortable test buy, Build is the serious-but-doable commitment, Improve is "less than one junior hire" — the framing that lets the owner sign without going to the family or the bank.

Product
Price (anchor)
What's included
What's not
Diagnostic
Free · 30 min
Scored conversation against a 10-question rubric · 1-page fit memo within 24h · pricing range for Review and Build
Custom analysis · proposals · NDA-bound deep dives
Review
Rp 15–25 jt · 2 wks · creditable
Process audit (3–5 workflows) · stack & data audit · prioritised plan · fixed-fee Build quote · 60-min readout · 12–18pg pack · fee credits 100% against Build if signed within 30 days
Implementation · vendor procurement · code · custom integrations
Build
Rp 80–200 jt · 6–10 wks
Sprint 0 + 3 build sprints + handover · integrations across existing tools · training session · 30-day post-launch adoption check
Net-new bespoke software · ongoing managed-service · strategic consulting outside the original Review scope
Improve
Rp 8–15 jt / month
Monthly performance review · adoption monitoring · prioritised iteration backlog (≤16 hrs/mo) · quarterly strategy session · access to WhatsApp / Slack channel
New module builds (sold as mini-Builds) · 24/7 support · vendor licensing
How the anchors map to the buyer's wallet
  • Review at Rp 15–25 jt, creditable against Build — frames as a refundable deposit, not a fee. Removes the "why pay you to scope what others give free" objection without losing the seriousness signal. ≈ one month of mid-tier marketing agency spend · keep-fees from the ~30% of Reviews that don't convert fund the Lead's Q1 time
  • Build at Rp 80–200 jt — material but doable. Sits in the same bucket as a renovation, a vehicle, or two months' payroll. we should always be able to point to a saved-cost or earned-revenue number ≥3× the Build price within 12 months
  • Improve at Rp 8–15 jt/mo — explicitly below one junior staff salary. That's the comparison we want the owner to make in their head. "a senior ops hire would cost me Rp 25 jt/mo and still need a system — Monkeybar IS the system, for half"
Review credit · discount rules · payment terms
  • Review fee, tiered by Build size — Rp 15 jt for Builds < Rp 100 jt · Rp 25 jt for Builds Rp 100–200 jt. The fit memo names the tier so the Review price is anchored before the Review SOW is signed.
  • Review credits 100% against Build — if the Build SOW is signed within 30 days of Review delivery. After 30 days the credit expires and Review converts to a keep-fee.
  • Case-study gift — Review fee waived for the first 2–3 wins in each lead vertical. Case-study capital is worth more than Rp 75 jt right now.
  • Discounting Build — up to 10% only when paired with a 12-month Improve commitment, not in isolation. Discount applied after the Review credit, not on top of it.
  • Discounting Improve — 10% off if paid annually upfront. No other discounts.
  • Payment terms — Review: 100% on signing. Build: 50% on signing, 50% on Sprint 3 sign-off. Improve: invoiced monthly upfront.
  • FX note — at ~Rp 16,000/USD, ranges above are roughly: Review $0.9–1.5K · Build $5–12.5K · Improve $500–950/mo.
ii — Demand Generation

How leads enter the pipeline

Owner Monkeybar Lead, until BD hire in Month 4–6
Cadence Weekly pipeline review · monthly channel-mix review · quarterly rebalance
Success measure ≥8 booked diagnostics / week by end of Day 90 · channel mix no more than 60% from any single source
Four channels — weights and owners
  • 1. Outbound (40% of pipeline) — LinkedIn + email. Targeted by vertical and role. Sequenced: connect → soft value drop → diagnostic ask. Owner: Lead, then BD hire. 100 personalised contacts/wk → 8–12 replies → 3–5 diagnostics booked
  • 2. Partner channel (30%) — Alturian's existing portfolio + accountants, lawyers, fractional CFOs who serve our ICP. Revenue-share or referral fee. Owner: Alturian central + Lead. an accountant who keeps hearing "our reporting is a mess" is the highest-quality referral source we'll ever get
  • 3. Content / SEO (20%) — one anchor piece per month per vertical. The job is credibility, not traffic. Owner: Lead writes, Alturian content support edits. "7 reports every multi-branch F&B owner should have, and how to actually get them" — gated with the diagnostic CTA
  • 4. Referral (10%) — every Improve client gets asked at month 3 and month 9. Structured ask, not vibes. Owner: Lead. "who are 2 people in your network who'd benefit from this?" + we draft the intro for them
The diagnostic-as-loss-leader logic
  • What the diagnostic actually delivers — a fit score, a one-page memo, and a next-step recommendation. Even if there's no fit, the prospect leaves with a useful diagnosis. That's the integrity bar. memo includes: 3 things working well · 3 things broken · whether Monkeybar is the right fix or not
  • Why it qualifies — it forces the prospect to articulate their problem in our language. Anyone who can't fill in the rubric isn't a buyer yet.
  • Why it disarms — "free 30-min conversation, no obligation" gets past gatekeepers that "schedule a call to learn more about us" can't.
  • Conversion target — 50% of diagnostics → creditable Review within 14 days. If we hit 75%, we're under-qualifying upstream. If we hit 25%, the diagnostic or the credit framing isn't landing.
  • Defensive metric — diagnostic-no-show rate. Above 25% means our top-of-funnel is too loose.
ii — Demand Generation (cont'd)

From first contact to signed SOW

Five conversion stages — the same five questions for each
  • 1. Contact made — first touch. Trigger: outbound reply or inbound form submission. Owner: Lead. Artefact: CRM record + first-touch template. KPI: % of contacts that reply within 5 business days. target: ≥10% reply rate on outbound; ≥80% response within 24h on inbound
  • 2. Diagnostic booked — calendar held. Trigger: prospect picks a slot. Owner: Lead. Artefact: pre-diagnostic prep brief sent 48h before. KPI: book-to-show rate. target: ≥85% show rate · below that, prep brief is too thin or qualification is too loose
  • 3. Diagnostic done — conversation completed and memo sent. Trigger: 30-min call ends. Owner: Lead. Artefact: 1-page fit memo within 24h. KPI: memo-on-time rate. target: 100% — sending the memo late is the single biggest credibility leak in this funnel
  • 4. Review SOW signed — creditable engagement starts. Trigger: prospect accepts memo recommendation. Owner: Lead. Artefact: 2-page Review SOW with credit clause + Build-decision deadline. KPI: diagnostic-to-Review conversion %. target: 50% · keep the contract short · always include the 30-day credit window and the Build-quote-due date
  • 5. Build SOW signed — the commercial peak. Trigger: Review readout delivered + Build quote accepted. Owner: Lead + Solutions Architect. Artefact: 4–6 page Build SOW with adoption clause + Review credit applied to the first invoice. KPI: Review-to-Build conversion %. target: 70% inside the 30-day credit window · always include the Improve retainer in the same SOW — separate signing flows lose 30–40% of attach
Common kill-signals — flag in the weekly review
  • Stage 1→2 leak > 70% — outbound message isn't speaking to the right buyer or the right pain.
  • Stage 3→4 leak > 50% — fit memo is too soft, the credit framing isn't landing, or we're not asking for the Review with conviction.
  • Build SOW signs without Improve — counts as a half-win, not a full win. Track separately.
iii — Delivery Engine

How projects get done predictably

Owner Solutions Architect (delivery quality) · Lead (commercial quality)
Cadence 2-week sprints · standup Mon/Wed/Fri · client check-in end of every sprint
Success measure ≥80% of Builds delivered on the original timeline · client adoption (active users / licensed users) ≥75% at Day 30 post-launch
A standard Build, sprint-by-sprint
Weeks 1–10
Sprint 0Re-scopeWks 1–2 · confirm Review · access
Sprint 1FoundationsWks 3–4 · core integrations
Sprint 2WorkflowsWks 5–6 · automate biggest pain
Sprint 3ReportingWks 7–8 · dashboards live
Sprint 4HandoverWks 9–10 · train, document
Day 30AdoptionMandatory check · trigger Improve
Quality bar — definition of done
  • Sprint demo passes the "client clicks it" test — the client uses the system in the demo, not us. If they can't navigate it, it's not done.
  • Every workflow has an owner on the client side, named in writing — no orphaned features. Adoption fails the moment something has no owner.
  • Documentation is in their tool, not ours — runbooks live in the client's Notion / Confluence / Drive, not Monkeybar's.
  • 30-day adoption check is in the SOW — non-negotiable. It's the bridge into Improve.
iii — Delivery Engine (cont'd)

Vertical-specific Build templates

Two templates so we don't quote each Build from scratch. The Solutions Architect tunes the template to the client; the template gives us 70% of the answer on Day 1 of Sprint 0.

F&B (multi-branch) — standard scope
  • Workflow 1 — sales reporting — daily branch sales auto-pulled from POS into a single dashboard. Owner per branch named. POS: Square / Toast / Storehub · pipe: native API or Zapier · destination: Looker Studio or Notion
  • Workflow 2 — loyalty & CRM — customer database unified across branches. Loyalty redemption tracked centrally. stamp-card or app-based loyalty merged into one CRM table
  • Workflow 3 — inventory & ordering — re-order points and stock-out alerts. Reduces 80% of "we ran out of X" calls.
  • Build KPIs — branch-level reporting time < 10 min/day; central monthly report time < 2 hrs; loyalty redemption rate visible per branch.
  • Improve focus — month 2: predictive re-order; month 6: per-branch margin attribution.
Real Estate (5–25 agent brokerage) — standard scope
  • Workflow 1 — lead capture & routing — every inbound enquiry (web, portal, WhatsApp) lands in the CRM and gets auto-assigned by territory or specialism. CRM: HubSpot / Pipedrive · routing rules: territory + agent capacity · SLA: agent contacts lead < 15 min
  • Workflow 2 — transaction pipeline — a single pipeline view across all agents with stage-by-stage SLAs and document tracking.
  • Workflow 3 — commission & reporting — agent dashboards (their pipeline, their commission run-rate) + brokerage P&L view.
  • Build KPIs — lead response time < 15 min, pipeline visibility per agent, commission reporting cycle < 2 days.
  • Improve focus — month 2: lead-source ROI tracking; month 6: agent productivity benchmarks.
Why two and not six

Templates compound only if we run them often. Two templates × three Builds each by Day 90 = six iterations of each playbook — enough to stabilise. Spreading across six verticals means every Build is bespoke and the engine never gets sharper.

iii — Delivery Engine (cont'd)

Tools & tech stack

Monkeybar's pitch is "we make the tools you already have actually work together." So we are tool-pluralist by design. But internally, we have a default stack — that's how we move fast and keep our own house in order.

Category
Monkeybar default
Recommended for clients
Acceptable alternatives
CRM
HubSpot (Starter)
HubSpot · Pipedrive · Zoho CRM
Whatever they already have, if it can integrate
Workflow / automation
Zapier + n8n (self-hosted for client builds)
Zapier · Make.com · n8n
Native integrations always preferred where they exist
Reporting / BI
Looker Studio + Notion
Looker Studio · Metabase · Power BI
Tableau if they're already paying for it; otherwise no
Project mgmt (internal)
Linear · weekly cadence
N/A — we use the client's tool
Comms (with client)
Slack Connect (preferred) · email fallback
Slack · Teams
WhatsApp only for one-off check-ins, not delivery
Docs & runbooks
Notion (Monkeybar workspace)
Always in client's tool
Notion · Confluence · Google Drive
Stack governance
  • Monkeybar's internal stack is the Solutions Architect's call — change it only with Lead sign-off. We don't want each pod inventing its own.
  • Client stack additions need a Build SOW line — never silently introduce a new paid tool into a client's environment. Visibility on cost = trust.
iv — Team & Org

Who runs Monkeybar, and what they own

Reporting line Monkeybar Lead → Alturian leadership · monthly business review
Initial headcount 4-person pod by end of Day 90: Lead + Solutions Architect + 2 Implementation Engineers
Success measure Pod can run two concurrent Builds without escalation; no role is a single point of failure beyond Day 120
Initial pod (4 roles)
  • Monkeybar Lead — owns P&L, owns sales, owns hiring, the BD until we hire one. Senior enough to close 6-figure SOWs and credibly Lead an SME owner conversation. profile: ex-strategy-consulting + 1–2 ops/tech roles · or ex-founder of a small consultancy
  • Solutions Architect — owns delivery quality, scopes Builds, runs Sprint 0. The most technical person in the room with clients; not a coder but understands integrations deeply. profile: ex-systems-integrator or senior CRM admin · 5–8 yrs experience · should be able to push back on the Lead's scoping
  • Implementation Engineer × 2 — does the actual building. Configures CRMs, builds Zapier/n8n flows, wires up dashboards. Different from a software engineer. profile: HubSpot or Salesforce admin background, automation-savvy, comfortable with APIs but not writing production code
Roles deferred — pulled from Alturian central or fractional
  • BD / Sales — Lead does this until pipeline justifies a full-time hire (target: ≥12 diagnostics/wk for 8 wks).
  • Designer / UX — pulled from Alturian shared services on demand. Used mostly for the dashboard layer.
  • Content / SEO — Lead writes; Alturian's content function edits and publishes.
  • Finance / Ops — fully shared with Alturian central. Monkeybar runs the same finance stack (invoicing, expense, payroll) as the rest of the group.
  • Recruiting / Talent — first 2 hires sourced via Alturian's network; agency only if vacancy > 6 weeks.
  • Legal / contracts — Alturian legal owns the SOW and Improve templates; Monkeybar Lead executes from the templates without back-and-forth.
iv — Team & Org (cont'd)

Hiring sequence & trigger conditions

Hire when a metric demands it, not on a calendar. Each role below has a trigger — pull the trigger only when the metric crosses the line for two consecutive weeks.

Role
Target start
Trigger to hire
First 60 days they own
Lead
Day 1 — appointed before this plan goes live
N/A — Day 1 prerequisite
Lock ICP, lock pricing, run first 10 diagnostics personally
Solutions Architect
Month 2
First Build SOW signed (or imminent)
Run Sprint 0 of first Build · own delivery template v1
Implementation Engineer #1
Month 2–3
First Build moves into Sprint 1
Ship Sprint 1 + 2 of first Build
Implementation Engineer #2
Month 4
Second Build SOW signed · or first Improve retainer live
Take Improve workload off Eng #1 · ship Sprint 1 of Build #2
BD / Sales
Month 5–6
≥12 booked diagnostics/wk for 8 consecutive weeks · Lead's calendar >60% on sales
Take outbound off Lead · own diagnostic-to-Review conversion
Hiring discipline
  • Don't hire to plan, hire to load. Pulling a trigger early is the cheapest way to break the P&L in Year 1.
  • The Lead doesn't backfill themselves. If the Lead is doing Implementation Engineer work in Month 5, something is wrong upstream.
v — Operating Cadence & Metrics

How we know it's working

Owner of metrics Monkeybar Lead
Reporting cadence Weekly internal · monthly to Alturian leadership · quarterly board-style review
Decision rights Lead decides inside the plan · changes to ICP, pricing, or P&L target need Alturian sign-off
Operating rituals
  • Weekly — Pipeline review (Mon, 30 min) — every diagnostic/Review/Build movement. Outcome: who picks up what this week. attendees: Lead + Solutions Architect once hired
  • Bi-weekly — Sprint review (Fri end of sprint) — per Build, with the client in the room. Outcome: sign-off on demo + commitments for next sprint.
  • Monthly — Business review (1st Mon of month) — full P&L vs plan, channel mix, conversion funnel. Outcome: 1–3 fixes for the month. a single Notion page · same template every month
  • Monthly — Improve client review — every Improve retainer client gets a 30-min monthly. Non-negotiable; this is the retention engine.
  • Quarterly — Strategy review — ICP still right? Pricing still right? Channel mix still healthy? Outcome: changes to the plan or a confirmation it stands.
KPIs — the dashboard
  • North-star — annualised ARR from Improve retainers. Reviewed monthly. Day 90 target: Rp 10 jt MRR (1 Improve · proof of motion) · Month 12 target: Rp 80 jt MRR (≈8 retainers)
  • Leading indicators (weekly) — diagnostics booked, diagnostic→Review %, Review→Build %, Build attach-rate of Improve, Build adoption at Day 30.
  • Health indicators (monthly) — gross margin per Build, hours-per-Build vs estimate, NPS, channel mix.
  • One client-promise metric — pick the impact claim from the website (4–6 hrs/wk saved) and measure it for every Improve client. If we can't prove it, the website is fiction.
v — Operating Cadence & Metrics (cont'd)

Year 1 P&L — the financial shape of success

A working illustration in IDR, not a forecast. The point is the structure: how revenue stacks at Jakarta SMB price points, what the local cost line looks like, and what break-even depends on. Numbers are anchors — Lead refines in Week 1.

Line
Q1 (illustrative)
Q2
Q4 — exit run-rate
Reviews delivered
3 × Rp 25 jt = Rp 75 jt
5 × Rp 28 jt = Rp 140 jt
8 × Rp 30 jt = Rp 240 jt
Builds delivered
1 × Rp 100 jt = Rp 100 jt
3 × Rp 110 jt = Rp 330 jt
5 × Rp 120 jt = Rp 600 jt
Improve MRR (end of period)
Rp 10 jt MRR (1 retainer)
Rp 35 jt MRR (3 retainers)
Rp 80 jt MRR (8 retainers)
Quarterly revenue
~Rp 190 jt (~$12K)
~Rp 540 jt (~$34K)
~Rp 1.08 B (~$67K)
Direct cost (pod salaries)
~Rp 180 jt (2 FTE)
~Rp 270 jt (3 FTE)
~Rp 380 jt (4 FTE)
Contribution margin
~5% — break-even
~50%
~65%
Annualised exit run-rate
~Rp 4.3 B / yr (~$270K)

Pod salary assumption: Lead Rp 40 jt/mo · Solutions Architect Rp 30 jt/mo · Implementation Engineer Rp 18 jt/mo (Jakarta market, May 2026). USD ≈ Rp 16,000.

Review numbers above show gross fees collected. Under the credit mechanic (slide 6), fees from Reviews that convert to Build credit 100% against the Build invoice — so the two rows partially overlap. At the Q4 conversion target (~70% of Reviews convert), net Q4 revenue lands closer to ~Rp 906 jt than the Rp 1.08 B sum, and contribution margin compresses ~7pp. The trade is intentional: cash arrives earlier, customer-experience friction drops, and Review→Build conversion lifts well enough to deliver more Builds at any given pod size.

What break-even depends on
  • Build attach rate of Improve — every Build without Improve is a one-off project; we need ≥70%.
  • Build delivery on schedule — every week of overrun on a fixed-fee Build burns ~3 percentage points of margin.
  • Improve churn — keep monthly churn under 3% in Year 1; one churn at Month 2 wipes out three months of work to acquire.
What kills it
  • Selling Builds without Improve — looks like revenue, runs the business as a project shop.
  • Bespoke Builds outside the two templates — every "we'll figure it out" Build is a 30%+ margin cut.
  • Adding the third vertical too early — splits team focus, no template compounding.
vi — First 90 Days

Week-by-week

Three phases. Each phase has a small number of things that must happen — everything else is optional. If a phase milestone slips, that's the cue to slow the next phase, not to skip ahead.

Phase 1 Days 1–14 Stand up the chassis
  • Lead appointed — first prerequisite. Without this, none of the rest happens.
  • ICP locked + pricing locked — published internally · Alturian leadership signs off.
  • Diagnostic rubric finalised — 10-question scorecard, fit memo template, 24h SLA.
  • SOW templates ready — Review SOW (2pg), Build SOW (4–6pg with Improve clause), Improve agreement.
  • First 50 outbound targets identified — 25 F&B + 25 Real Estate, named contacts.
  • Internal tooling live — HubSpot, Linear, Notion, Slack — all set up under the Monkeybar workspace.
Phase 2 Days 15–42 Prove the funnel
  • 10 diagnostics completed — Lead does these personally. No delegation.
  • 2 paid Reviews signed and delivered — even if pricing has to flex, get the first two on the books.
  • 1 Build SOW signed — Improve retainer attached in the same SOW.
  • Solutions Architect hired and onboarded — they own Sprint 0 of Build #1.
  • First case study draft — written from the first Review delivered, even before Build is done.
Phase 3 Days 43–90 Prove delivery + the prize
  • First Build delivered on time — passes the "client clicks it" demo test.
  • First Improve retainer live — the moment the business model is real.
  • Implementation Engineer #1 hired — Lead is no longer the constraint on delivery.
  • Pipeline at ≥8 booked diagnostics/wk — sustained for at least 4 of the last 6 weeks.
  • Two case studies published — one F&B, one Real Estate.
  • 90-day review with Alturian leadership — go / hold / pivot.
vi — First 90 Days (cont'd)

Definition of "operating" · out of scope · open questions

By Day 90, "operating" means
  • ≥2 paid Reviews delivered, with fit memos, readouts, and Build quotes.
  • ≥1 Build live, with a passed adoption check at Day 30 post-launch.
  • ≥1 Improve retainer signed — the model is real, not theoretical.
  • 3-person pod in place — Lead + Solutions Architect + Implementation Engineer #1.
  • Weekly pipeline ritual functioning — the dashboard is real and reviewed without prompting.
  • Two published case studies — one per lead vertical.
  • A 90-day review document — written by the Lead, decided by Alturian leadership, that says: continue / hold / pivot.
Explicitly out of scope (Days 1–90)
  • Vertical #3 — not even a pilot. Park it.
  • Geographic expansion — one country until 5 wins in-market.
  • Productized offerings beyond the four-product ladder — no "Monkeybar Audit Lite", no "Monkeybar Academy."
  • Formal brand refresh — current site is good enough for the first 90 days.
  • Hiring a BD person — Lead does sales until the volume forces the hire.
  • Custom software development — if a Build needs it, scope as a separate engagement and consider passing.
Open questions for Alturian leadership — push back on these
  • Lead — do we have one in mind? If yes, we go now. If no, lining one up is the gating item before any of this starts.
  • Verticals — F&B + Real Estate is a proposal. If Alturian's portfolio gives us a stronger warm-intro path into a different pair, swap.
  • Year 1 capital — working capital to cover the Months 1–5 dip is ~Rp 200–250 jt (recovered from Q2 onward). Open question is whether Alturian wants to add headroom for marketing, contingency, or accelerated hiring inside the same envelope. Pod size and hiring sequence are tunable around it.
  • Internal customer #1 — is there an Alturian portfolio business willing to be the first case study? That collapses the first 30 days dramatically.
Appendix A1 — The first 14 days

What goes in the calendar tomorrow morning

Not "what the plan says" — the literal hour-by-hour. By Day 14, the funnel is moving and the SA hire is open.

Day 1 Solo · prep day Set up the workspace before talking to anyone outside
  • 09:00–10:00 — Set up: Monkeybar email, HubSpot Starter, Linear, Notion, Calendly, Slack workspace. Day-1 expense list to Alturian finance.
  • 10:00–11:00 — Block recurring slots: weekly pipeline review (Mon 09:00) · monthly business review (1st Mon 14:00) · quarterly strategy (last Fri of Q).
  • 11:00–13:00 — Read this plan end-to-end; note 5 things to push back on at the Day-14 sync with Alturian leadership.
  • 14:00–17:00 — Build v0 outbound list: 50 named contacts (25 F&B + 25 RE), each with name, role, company, "why them" line, source.
  • 17:00–18:00 — Send a one-page launch memo to Alturian leadership: who you are as Lead, what you're locking in Week 1, what you need from them by Week 2.
Days 2–7 Build the engine Stand everything up, then start the outreach motor
  • Day 2 — Lock the diagnostic rubric (Appendix A2) and the fit-memo template. Run a dry run with an Alturian colleague playing prospect.
  • Day 3 — Configure HubSpot: 8 pipeline stages + 6 custom properties (Appendix A5). Import the v0 outbound list.
  • Day 4 — Customise outbound scripts (Appendix A3) to your voice. Show two colleagues; iterate twice.
  • Day 5 — Send first 25 outbound contacts (12 F&B + 13 RE). Calendly link in every message. Check inbox 11:00, 14:00, 17:00.
  • Day 6 — Brief Alturian central: which portfolio companies have warm intros to F&B / RE owners? Capture 5 referral candidates.
  • Day 7 — Friday wrap-up. Stats: % opened, % replied, # diagnostics booked. Tweak Wave-2 message based on patterns.
Days 8–14 First diagnostics, first refinements Run the funnel against real prospects, refine the templates
  • Days 8–10 — Run 3–5 diagnostics. Send the fit memo within 24h every time. Note which questions land flat — refine.
  • Day 11 — Send Wave 2 outbound (next 25 contacts). Adjust based on Wave-1 reply patterns.
  • Day 12 — Open SA hiring: post JD on LinkedIn, ping 5 candidates from Alturian's network.
  • Day 13 — Run 2–3 more diagnostics. Send first paid Review proposal — target: 1 signed by Day 21.
  • Day 14 — Day-14 sync with Alturian leadership: funnel stats, the 5 Day-1 push-backs, the asks for Days 15–60.
Appendix A2 — Diagnostic rubric

The 10 questions, scored — and what the memo looks like

The 10 questions · score 0–4 each · /40 total
  • 1. Outlets/agents now & in 12 months? Sweet spot 3–15 outlets / 5–25 agents = 4 · single-unit or 50+ = 1.
  • 2. What systems are in your stack today? Some tools but not integrated = 4 · nothing = 2 · already fully integrated = 1.
  • 3. How does data flow between them? Manual copy-paste = 4 · spreadsheet bridge = 3 · partial automation = 2 · already automated = 1.
  • 4. How do you measure branch/agent performance today? Weekly manual report = 4 · ad-hoc = 4 · monthly = 3 · live dashboard = 1.
  • 5. % of your week spent chasing reports/data? 30%+ = 4 · 10–30% = 3 · <10% = 1.
  • 6. Biggest operational pain to fix in 90 days? Specific, named, measurable = 4 · vague = 1 · "everything" = 2.
  • 7. Tried solving this before? What broke? Tried, has a clear story = 4 · never tried = 3 · tried, blames vendor only = 1.
  • 8. Who'd own the solution day-to-day on your side? Named person, has capacity = 4 · TBD = 1 · "the owner" = 2.
  • 9. Budget envelope for fixing this? Rp 100–250 jt + monthly = 4 · <Rp 50 jt total = 1 · "depends" = 2.
  • 10. What does "this worked" look like in 6 months? Concrete metric named = 4 · vague vision = 1.
Fit memo · sent within 24h · 1 page
  • To Pak/Bu [name] · Re Diagnostic findings · Score 31/40 · Recommendation Ready for Review
  • Three things working well — POS data is clean; outlet-level P&L is captured monthly; the ops manager is sharp and would own this.
  • Three things broken — branch reporting takes ~12 hrs/week of manual work; loyalty data is fragmented across 8 outlets; no live view of stock-out incidents.
  • What we'd do — 2-week paid Review (Rp 25 jt) to map the 3 highest-pain workflows, deliver a fixed-fee Build quote and a prioritised plan. Likely Build range: Rp 100–140 jt over 6–8 weeks.
  • If we're not the right fit — for fully bespoke software, talk to [partner]; for pure marketing, talk to [partner].
  • Next step — Calendly link to book Review kickoff. Decision deadline: 14 days.
Score thresholds — what to do
  • <16 — disqualify. Send a polite no-fit memo (still useful: 3 working / 3 broken). Refer to a partner if relevant.
  • 16–25 — watchlist. Memo + a 60-day check-in calendar invite. Track in HubSpot.
  • 26–32 — ready for Review. The default outcome we're underwriting.
  • 33–40 — rare. Pitch Review + a Build option in the same memo; close inside 7 days.
Appendix A3 — Outbound & objections

Verbatim scripts — and how to handle the 8 most common pushbacks

Outbound — copy, adapt with one named detail
  • LinkedIn · F&B — "Hi [Name], saw [brand] is at [N] outlets now — that's the size where multi-branch reporting starts feeling like a second job. We help Jakarta F&B owners turn that into 10 minutes a day. Open to a 30-min diagnostic — free, no pitch?"
  • Email · F&B · subj: "Multi-branch reporting in 10 min/day" — "Hi [Name], at [N] outlets, manual reporting tends to swallow a day a week. We typically save F&B owners 4–6 hrs weekly within 8 weeks — by working with the tools they already have, not replacing them. 30-min diagnostic, free, written memo within 24h. Calendly: [link]."
  • LinkedIn · RE — "Hi [Name], at [brokerage]'s size, leads tend to go cold because routing is slow and pipeline visibility is thin. We help Jakarta brokerages 5–25 agents fix that in 6–8 weeks. 30-min diagnostic, free?"
  • Email · RE · subj: "Lead response < 15 min, every time" — "Hi [Name], the brokerages we work with had two recurring pains: leads sat >1 hr before an agent responded, and owners had no live pipeline view. We typically fix both in 6–8 weeks. 30-min diagnostic, written memo within 24h. Calendly: [link]."
  • Follow-up rule — 1 follow-up after 4 business days, 1 final after 8. Then the contact moves to "nurture" (Q+1 outreach).
8 standard objections · one-line responses
  • "We can just hire someone." → Hiring adds a person; we add a system that frames what every person does. The system stays when the person leaves.
  • "We tried something like this; didn't work." → What broke — the tools, the rollout, or the adoption? Most failures are #3, not #1.
  • "We can't afford it." → Compare to one junior hire (Rp 15–25 jt/mo). Which gives more leverage?
  • "We need to think about it." → Sure. What's the next concrete decision you'd take in the next 14 days?
  • "Just send a proposal." → The diagnostic IS the start of that. 30 min, then a written memo within 24h — sent whether or not we're a fit.
  • "Your competitor is cheaper." → What's their adoption SLA — do they walk away the day the system goes live, or stay 30 days through it?
  • "We have a CTO who handles this." → We work alongside the CTO, not instead. We're the integration and adoption layer, not the codebase.
  • "Not a priority right now." → Fine. Cost of waiting 6 months ≈ [N] hrs/wk × [Lead's salary]. Want a follow-up in 60 days?
Volume targets — until BD hire in Month 5–6
  • Wave size — 25 contacts per wave, two waves per week (50/wk).
  • Reply rate target — ≥10% (5/wave). Below 5%, the message is broken — pause and rewrite.
  • Diagnostic-booked rate — ≥30% of replies (1.5/wave). Below 20%, the intro needs to be sharper.
  • Pipeline result — 8 booked diagnostics/wk by Day 90, of which ≥6 show up.
Appendix A4 — Sprint-by-sprint Build playbook

Per-sprint rhythm — meetings, artefacts, sign-off

Sprint
Meetings
Artefacts shipped
Definition of done
Sprint 0 · Wks 1–2
Kickoff (Day 1, 90 min, owner + key team) · stack walkthrough (Day 3, 90 min) · Sprint 0 sign-off (Day 10, 60 min)
Sprint 0 brief · access matrix · integration map · risk log
Owner signs Sprint 0 brief; SA confirms Build is feasible at quoted scope. If not, re-quote or refund.
Sprint 1 · Wks 3–4
Standup MWF (15 min, internal) · Friday demo (30 min, with client) · sign-off (30 min, Friday Wk 4)
Core integration #1 live · staging dashboard with first data flowing · Loom walkthrough
Client logs in, clicks through dashboard unaided, signs Sprint 1 sheet.
Sprint 2 · Wks 5–6
Same cadence + a mid-sprint check (Tue Wk 6) when the heaviest workflow goes live
Biggest workflow live (POS→CRM for F&B; lead routing for RE) · runbook v1
Workflow runs without manual intervention for 5 consecutive days.
Sprint 3 · Wks 7–8
Same cadence · final demo with the owner present (Friday Wk 8)
Reporting layer live · all KPIs visible · runbook v2 in client's docs tool
Client uses reports in their actual weekly meeting; we observe at least once.
Sprint 4 · Wks 9–10
Training workshop (3 hrs · all relevant team) · handover meeting (Day 70) · Improve kickoff
Final runbook · training recording · adoption-tracking sheet · Improve SOW signed
Client team owns 100% of operations; SA can step out without escalation for 2 weeks.
Day 30 post-launch
Adoption review (60 min, with the client team)
Adoption report · iteration backlog for Improve · case-study draft
Active users / licensed users ≥75%; if not, on-site adoption week before Improve starts.
Stop-the-line rules
  • Sprint 0 fails sign-off — pause, re-quote or refund. Don't push through; it never gets better.
  • Two consecutive sprints overrun by >3 days — Lead joins next standup; SA presents a recovery plan within 48 hrs.
  • Adoption <40% at Day 30 — Improve cannot start; SA runs an on-site adoption week before retainer kicks in.
Appendix A5 — Pipeline configuration & MBR

CRM pipeline + the 1-page monthly business review

HubSpot pipeline — 8 stages
  • 1. Lead — identified, not yet contacted. Owner: Lead/BD.
  • 2. Outreach Sent — first message out. Auto-advance after 5 days if no reply.
  • 3. Diagnostic Booked — calendar held. Auto-prep brief sent 48h before.
  • 4. Diagnostic Done — call complete · memo sent within 24h. Score logged.
  • 5. Review Sold — Review SOW signed and 50% paid upfront.
  • 6. Build Sold — Build SOW signed, kickoff scheduled. Improve attached or noted.
  • 7. Build In Flight — Sprint 0 started. Tracked separately in Linear.
  • 8. Improve Live — retainer active. Tracked monthly.
6 custom properties + Closed/Lost reasons
  • Vertical — F&B / Real Estate / Other (Other = flag, don't pursue).
  • Outlets / agents — number, drives ICP fit.
  • Buyer role — Owner / Ops Director / GM / Other.
  • Diagnostic score — 0–40, mandatory after Stage 4.
  • Source — outbound · partner · content · referral · inbound.
  • Next action date — mandatory; surfaces in weekly pipeline review.
  • Closed/Lost reasons — disqualified · no-show · lost to competitor · lost to "do nothing" · timing.
Monthly Business Review · 1-pager · same template every month
  • 1. Funnel (5 numbers) — leads created · diagnostics done · Reviews sold · Builds sold · Improve net new.
  • 2. P&L vs plan — month + YTD revenue, cost, contribution margin · vs the table on slide 15.
  • 3. Channel mix — % of pipeline from outbound / partner / content / referral. Flag if any >60%.
  • 4. Build & Improve health — Builds on time? · adoption metrics on live Builds · Improve churn · NPS.
  • 5. Top 3 issues — what's broken or risky this month.
  • 6. Top 3 decisions needed — explicit asks of Alturian leadership.
Appendix A6 — Risk register & cash flow

Top risks, escalation rules, Year 1 cash curve

Risk
Likelihood
Impact if it hits
Mitigation
Lead resigns / burns out before Day 90
Medium
Critical — full reset
Alturian co-Lead presence in monthly review · capped weekly hours · documented playbooks (this doc) so handover is not catastrophic
First Build overruns >2 wks
High in Q1
~30% margin hit · case-study delay
Mandatory Sprint 0 sign-off · weekly burn check · stop-the-line rule (Appendix A4)
Improve attach rate <50%
Medium
Project shop, not a business
Improve baked into Build SOW, not sold after · monthly review rejects Builds without it
Diagnostic→Review <15%
Medium in Q1
Funnel collapses
Rebuild rubric · 5-dialogue test · sharper outbound qualification upstream
Outbound reply rate <5%
Medium
Pipeline goes dark
Rotate message format weekly · increase partner-channel weight to 40%+ temporarily
Implementation Engineer hire fails
Medium
SA bottleneck · Builds stack up
2-month probation · backup pull from Alturian central · second candidate kept warm
Client escalation / Build dispute
Low
Reputational + cash hit
Written escalation path in SOW · Lead + SA both at sign-off · Alturian legal on retainer
FX shift — IDR weakens vs vendor costs
Low–Medium
~5–10% margin compression
Lock vendor licenses in IDR where possible · quarterly FX review · pass >15% moves to client renewals
Escalation rules — when Lead calls Alturian leadership
  • Within 24h — any client dispute >Rp 25 jt · any Build sprint that fails sign-off · Lead unable to make payroll next month.
  • Within the next monthly review — funnel below half of plan for 2 consecutive months · margin below 30% for 2 consecutive months · any senior departure.
  • Quarterly — any pricing change · any new vertical pilot · capital ask above the Year 1 envelope.
Year 1 cash curve · indicative · IDR jt
  • Months 1–2 — net cash negative (~Rp 60 jt/mo burn). Salaries + tools, no revenue yet.
  • Month 3 — first Review payment in (Rp 12.5 jt 50% upfront) · Build #1 50% upfront (Rp 50 jt). First positive month possible.
  • Months 4–5 — 2 more Reviews · Build #1 progressing · first Improve live. Cash position recovering.
  • Month 6 — break-even on cumulative cash. Pod is 3 FTE.
  • Months 7–9 — net cash positive each month · cumulative position climbing fast.
  • Months 10–12 — exit Year 1 with ~Rp 200–300 jt cash buffer · ARR ~Rp 1B run-rate from Improve alone.
  • Capital ask Year 1 — Alturian funds ~Rp 200–250 jt working capital to cover Months 1–5 dip; recovered from Q2 onward.
Appendix B — Glossary

Glossary of terms

Plain-English definitions for the jargon used above. Skim or search as needed.

Adoption
The percentage of licensed users who actively use a system after launch. Our floor is 75% at Day 30 — below that, the Improve retainer cannot start.
API Application Programming Interface
The technical contract a software tool exposes so other tools can connect to it. We use APIs to wire integrations between client systems.
ARR Annualised Recurring Revenue
Monthly recurring revenue × 12. The standard way to size a subscription business. Our north-star metric tracks Improve ARR.
BD Business Development
Sales-adjacent function focused on acquiring new clients and partnerships. The Lead does this until pipeline justifies a full-time hire.
BI Business Intelligence
Software that turns raw data into reports and dashboards (Looker Studio, Metabase, Power BI).
Break-even
The point at which cumulative revenue equals cumulative cost — the first month the business stops eating cash.
Burn / cash burn
Net cash consumed per month. "Rp 60 jt/mo burn" means we spend Rp 60 jt more than we collect that month.
Contribution margin
Revenue minus the direct cost of delivering it. Tells you how much each rupiah of sales contributes after pod salaries.
Credit mechanic (Review credit)
Our pricing rule: the Review fee credits 100% against the Build invoice if Build is signed within 30 days. Frames Review as a refundable deposit, not a separate charge.
CRM Customer Relationship Management
Software to track contacts, deals, and customer interactions (HubSpot, Pipedrive, Salesforce).
DoD Definition of Done
The explicit bar a piece of work must clear to be considered complete. Each sprint has its own.
F&B
Food & Beverage. One of our two lead verticals — multi-branch operators with 3–15 outlets.
Fit memo
The 1-page output of every Diagnostic — score, what's working, what's broken, recommendation. Sent within 24h of the call.
FX Foreign Exchange
Currency rate. Relevant because most software vendors price in USD while we earn in IDR.
Greenfield
A system built from zero with no existing tools to integrate. Monkeybar explicitly does not do greenfield — we work with what's there.
ICP Ideal Customer Profile
The precise sub-segment within a vertical we sell to. Defined by size, role, geography, willingness to pay.
jt juta
Indonesian for "million." Rp 25 jt = 25 million rupiah ≈ $1,560 at Rp 16,000/USD.
Keep-fee
The Review fee we retain when a client doesn't proceed to Build within the 30-day credit window. Funds the Lead's time spent on non-converting Reviews.
KPI Key Performance Indicator
A metric that drives a decision. If a metric doesn't change a decision, it's reporting overhead.
Lead
Two senses: (1) a prospective customer at top-of-funnel; (2) the senior person running Monkeybar.
MBR Monthly Business Review
The standardised 1-page monthly readout from the Lead to Alturian leadership.
MRR Monthly Recurring Revenue
Sum of monthly retainer fees from active Improve clients. Multiply by 12 to get ARR.
NPS Net Promoter Score
The standard "would you recommend us" metric, scored –100 to +100.
P&L Profit & Loss
The financial statement showing revenue, costs, and profit over a period.
POS Point of Sale
The till / register system at an F&B outlet (Square, Toast, Storehub). Source of sales data.
RE Real Estate
Our second lead vertical — brokerages with 5–25 agents.
Retainer
A recurring monthly fee for ongoing service. Improve is sold as a retainer.
Run-rate
Annualising a current period to project forward. "Q4 exit run-rate" = Q4 revenue × 4.
SA Solutions Architect
Second hire after the Lead. Owns delivery quality, scopes Builds, runs Sprint 0.
SLA Service Level Agreement
A written commitment to a response or quality standard (e.g., "agent contacts lead within 15 min").
SME / SMB Small/Medium Enterprise / Business
Businesses below mid-market. For our ICP: roughly Rp 5–50 B annual revenue, 50–500 staff.
SOW Statement of Work
A short contract describing what Monkeybar will deliver, by when, for how much. Review SOW is 2 pages; Build SOW is 4–6 pages.
Sprint
A fixed 2-week unit of work with a clear input, deliverable, and demo at the end.
Sprint 0
The first sprint of any Build — re-confirms scope, sets up access, locks the integration plan. Failing Sprint 0 means the Build doesn't proceed.
Stack
Shorthand for the set of software tools a business uses. "Their stack is HubSpot + Zapier + Looker."
Stop-the-line
A rule that halts work when a tripwire fires (e.g., adoption <40% at Day 30). Borrowed from Toyota production.
Watchlist
Diagnostic-scored prospects who weren't ready for Review but worth re-approaching in 60 days.