For the people who hired them

In the loop —
without ever asking.

Your contractor runs on Mango. You get approved updates in the chat you already use — no portal, no password, no “any update?” pings.

How it works ↓ Request a seat

I do the work I hired the contractor

Contractor already on Mango? Your invite link comes from them — connecting is instant. Not yet? Request a seat and we'll bring them aboard together.

💬 Your own AI chat

You 9:02 AM

what's the latest on my project?

Mango 9:02 AM

This week: 14.5h on your project — onboarding flow shipped, demo on track for Thursday. Invoice #12 is pending, due in 9 days.
From the update your contractor approved yesterday.

Private beta · for the diligent contract developer

Your day was planned
before you woke up.

Mango posts your kickoff in Slack at 7:00 — ranked plan, stale-PR flags, income pace. Reply to change it; 👍 to lock it.

Request a seat See it work ↓

I do the work I hired the contractor

💬 #your-planning-channel

Mango APP 7:01 AM

☀️ Morning Kickoff — Fri 7/10
• Acme — ship onboarding [in progress]
• Vertex — funnel audit [planned]
🔀 PR #128 open 2.3bd — over the <2bd target
💵 Income WTD $1,240 vs pace $1,440
Reply with changes, or 👍 to lock the plan as-is.

You 7:14 AM

swap the audit for the TikTok submission — it's due today

Mango APP 7:14 AM

Got it — plan updated ✅ Go do the work.

★ Built for contractors

The outcomes, at a glance

Results that show up whether or not you remember to log in.

Ship more than you can type 🚀

An objective becomes a reviewed pull request.

+ def authorize_share(client, kind):

+ return SharedReport.frozen(payload)

- # TODO: gate the client view

✓ PR #128 opened

code-kanban/onboarding → main

Your day, decided 🧭

Ranked before coffee.

✓ Acme — ship onboarding

✓ Vertex — funnel audit

○ Invoice Northwind

Cash, in view 💸

Know what's coming, before it lands.

Updates write themselves ✍️

You just approve — it never auto-sends.

Weekly update · Acme — Approved ✓

Outcomes > hours 🎯

The grade rewards real progress.

🤝 Trust, by design

What Mango will never do

The boundaries are the feature. Everything else is built inside them.

Message a client on its own

Everything client-facing waits for your one-tap approval. Nothing auto-sends. Ever.

Merge its own code

Coding runs end in a reviewed pull request. You are the only one who merges.

Guess your numbers

Money math is deterministic — rates, invoices, pace. The AI narrates; it doesn't arithmetic.

✓ And when the AI is unavailable, every answer degrades to a plain deterministic fallback — it never bluffs.

⚙ One machine

Your tools, working as one

Connect what you already use. Mango listens across all of it and keeps your plan current — so the to-do list writes itself.

Clockifyevery hour you track

Slackwhat clients ask for

Fathomwhat you promised on calls

WhatsAppthe “can you also…”

↓

🥭 Mango reads it all — and rewrites your day

↓

Today● updated 2 min ago · automatically

✓ Send Acme the revised scope from Fathom call

○ Share staging link with Northwind from Slack

○ Invoice Vertex for last sprint from WhatsApp

🧠 Under the hood

Two layers make it feel like it knows your business

The plan only writes itself because of what sits underneath: a live context layer that never crosses clients, and a memory that actually remembers.

Context Fabriclive context, walled off per client

Live

Every Slack thread, WhatsApp message, meeting recap and work session flows into one place and stays current as it happens — so any chat answers from what's true right now, not last week.

AcmeSlack · WhatsApp · Fathom

NorthwindSlack · WhatsApp · Fathom

Each client's context is sealed in its own lane — bound to the workspace, number, or meeting it came from. One client's conversation can never surface in another's.

Company Braindurable memory of how you work

Live

The decisions you make and why, each client's quirks, your billing rules, the lessons you've learned — Mango curates them once and remembers. Every chat starts already knowing them, instead of asking again.

💡 Acme invoices are net-15, billed by milestone

💡 Northwind prefers updates in Slack, not email

💡 Add a 15% buffer to every new estimate

Knowledge accrues instead of resetting — so Mango gets sharper about your business the longer you use it.

🧠 The obvious question

Claude already knows everything. Except your business.

Claude alone

“As a rough estimate, a contractor at your rate might expect…” — plausible, generic, grounded in nothing.

Claude + Mango

“You're at 30.6 of 36h. Acme's invoice clears Friday. Vertex is eating your investment hours.” — your tracker, your invoices, your plan.

Mango is the memory and the measurements; your AI is the interface. That's why it works inside the chat you already have instead of another dashboard you'll stop opening.

📲 No new app to open

Call Mango from where you already work

Mango isn't one more tab to keep open. Ask it right inside the tools you already live in — and it answers with your real data.

ClaudeClaude Connector

● Live

what should I focus on today?

🥭 Acme onboarding — your only at-risk rock, due Thursday.

Request a seat →

Private beta — connector access (Claude Desktop, web, or Code) comes with your seat.

SlackSlack bot

● Live

@Mango did Northwind pay yet?

🥭 Not yet — $2,400, 6 days out. Want a nudge drafted?

See the daily loop ↓

@Mango answers in-thread from your real data — and runs your morning kickoff and evening shutdown as scheduled threads.

💬 New — live in Slack

Your business now runs a daily standup — in Slack

Mango opens your day, closes your day, and answers in-thread. Reply in plain English to reshape the plan; react 👍 to lock it. No dashboard required.

Morning Kickoff7:00 — today's plan + flags

Evening Shutdown21:00 — what shipped, tomorrow's top 3

Weekly KickoffMon — the week's baseline, locked

Weekly ReflectionFri — plan vs. what really happened

Reply to any thread and the plan updates. Ignore one and yesterday's plan carries forward — flagged, never lost. Every post is grounded in your real tracker, PRs, and income pace.

💬 #your-planning-channel

Mango APP 7:01 AM

You 7:14 AM

swap the audit for the TikTok submission — it's due today

Mango APP 7:14 AM

Got it — added “TikTok submission”, moved “funnel audit” to tomorrow. Plan updated ✅

Scheduled threads, written from your live plan — with KPI flags computed at post time.

💬 #acme-project

You 6:49 PM

@Mango what's running right now, and what's queued for tonight?

Mango APP 6:49 PM

One run live: onboarding flow on acme-web, 12 min in. Tonight's queue: test-hardening at 1:00, daily report at 9:30. Your only at-risk objective is the Thursday demo — want me to bump it to the top tomorrow?

Answers from your live data — plans, hours, invoices, KPIs, even what your coding agents are doing.

💬 #northwind-dev

You 2:12 PM

@Mango fix the login redirect loop on staging

Mango APP 2:31 PM

Done — traced it to a stale session check.
✓ PR #42 opened: fix(auth) — review when ready

A Slack ask becomes a reviewed pull request on that client's repo. You review; nothing merges itself.

🟠 You — the operator

The full loop: cadence threads, Q&A, coding runs, schedules. You grant everyone else's access.

🟢 Clients you invite

Ask @Mango questions in the channel you share — answers scoped to their project only. Coding rights are a separate, per-person grant.

⚪ Everyone else

Nothing. Access is deny-by-default, per person, per channel — a capability you never granted doesn't exist.

Each channel is bound to one client, so answers can never blend one client's business into another's.

🔄 One machine, two seats

How it all fits together

You run the work; your client stays in the loop. The same engine serves both — and nothing reaches your client until you approve it.

🟠 The contractor — you run the work

Your tools

Clockify hours
Slack & WhatsApp asks
Fathom calls
GitHub activity

→

🥭 Mangoreads it all and rewrites your day

→

What you get

A ranked daily plan
Draft client updates
Invoices & cash in view
Shipped code — reviewed PRs

↓

✋ You approve. Internal work — plans, briefs, drafts — generates automatically. Anything that reaches your client waits for one tap. Nothing auto-sends.

↓

🟢 The client — in the loop, without chasing you

A one-time link

You send it once
No portal, no password

→

Their own AIthey just ask in plain English

→

What they see

Weekly progress & pace
Daily updates
Invoices & overdue alerts
Read-only — only what you shared

For your clients

In the loop — without chasing you

A calm window for the people who hired you. Only what you approve.

How your window works

Approved updates, in your own chat

Your contractor reviews and approves each update; it appears where you already are.

●

In their own chat

Updates land in the client's AI — no portal, no meeting.

●

Only what you approve

You authorize each update. Live, un-reviewed data stays private.

●

Fewer "any update?" pings

The answer's already there. Trust goes up.

●

In your own chat

Connect once with the invite link — then just ask, in plain English.

●

Reviewed before you see it

Every update was approved by your contractor. No raw feeds, no noise.

●

Progress, pace & invoices

Weekly progress, whether work is on pace, and what's owed — read-only.

★ Powered by the BMAD Method

Every BMAD agent, in your Claude chat

Mango exposes the full open-source BMAD agent library through one connector — brainstorming, PRDs, architecture, UX, dev, QA, research and more. Run any of them, grounded in your real business data.

Built on the open-source BMAD Method · official documentation · full credit to the BMAD-METHOD project and its maintainers.

Loading the agent library…

Have an agent we're missing?

Tell us the custom agent you wish you had. We review every idea and build the best ones into Mango.

❓ Straight answers

Questions, answered honestly

What works today — and what's still on the way. We flag the difference.

🟠 For contractors — how you use Mango

How do I get access?Private beta

Mango is in private beta — we onboard a few contractors at a time, and first dashboard access goes to waitlist applicants. To apply, tell us about your use case: chat with our discovery agent right in Claude (quick three questions, or as detailed as you'd like — it's an open connector, no account needed), or just leave your email. Your clients don't need a seat — they join through your invite link once you're in (though clients can request seats too).

Is there a Mango “MCP,” and what is it?Live

Yes. Mango runs a small server that links your own Claude chat to your live Mango account. Ask your business anything in plain English — your plan, your hours, your cash, what a client just asked for — and act on it right there in the chat, grounded in your real data.

What can I actually do through it today?Live

Read and act on your operating picture: your ranked day and this-week pace, your objectives and how far each has progressed, hours by client, your cash projections and when invoices land, and the context that arrived across your connected tools (chat, call recordings, messages). You can also stage changes to your plan for review.

Can I plan a sprint and upload my existing plan?Live

Yes. Drop in a sprint workbook — no special template required. Mango reads it, maps it onto your plan, and shows you a diff; nothing changes until you confirm. Re-upload anytime and it updates tasks in place instead of duplicating them.

How do I interface with the plan?Live

Three ways, one plan underneath: the Mango web app, your Claude chat, or a single “sync this workbook” request. Use whichever fits the moment — they all read and write the same source of truth.

Can Mango write and ship the code for my tasks?Live

Yes. Connect a project's repository and Mango turns a planned task — or an @Mango ask in Slack — into an autonomous coding run that ends in a reviewed pull request on that repo, with the link posted back in-thread. Scheduled runs handle overnight work (test hardening, docs, reports) under enforced cost caps. You review every PR; nothing merges itself.

What does Mango do in Slack?Live

Four things: it runs your daily planning cadence (Morning Kickoff and Evening Shutdown threads, plus weekly kickoff and reflection) where a plain-English reply updates your plan and a 👍 locks it; it answers @Mango questions in-thread from your live data; it flags KPI breaches (stale PRs, income pace) inside those posts; and in channels you've connected to a repo, an @Mango ask can become a pull request. Access is per-person, per-channel, deny-by-default.

Will Mango message my clients or change things on its own?By design

No. Internal artifacts — plans, briefs, draft updates — generate automatically, but anything that leaves your hands is one-tap approval and never auto-sends. And every AI answer has a plain, deterministic fallback, so it degrades gracefully rather than guessing.

🟢 For clients — how you stay in the loop

Can I request a seat myself?Live

Yes. Request a seat and tell us about your project — we'll onboard you and your contractor together, so you can interface with them through Mango. If they're already on Mango you don't need one: ask them for your invite link and you're connected in minutes.

How do I get updates from my contractor?Live

In your own AI assistant. Your contractor mints a one-time connect link from your project's Overview tab in Mango and sends it to you — open it once and Mango is linked to your assistant. After that you just ask in plain English — “what's the latest on my project?” — and the answer's already there. No portal, no chasing.

Do I need a portal or a password?Live

No. There's nothing to log into — Mango answers inside the assistant you already use. The one-time connect link is the only setup.

What can I actually see?Live

Only what your contractor turns on, chosen per client. That can include weekly progress, daily updates, whether work is on pace, outstanding invoices, a cash forecast, and overdue alerts — all read-only.

Will I see their private or unreviewed data?By design

No. You see approved, scoped views only — their live working data, and anything they haven't shared, stays private. You get the picture without the noise.

Can I ask Mango questions in Slack?Live

Yes — if your contractor has allow-listed you. In the Slack channel you already share, mention @Mango and ask in plain English; answers are scoped to your project only. If you're not allow-listed, Mango simply doesn't respond to you.

Can I reply back or ask Mango to make changes?Roadmap

Partially. Asking questions in your shared Slack channel is live (above), and some clients are granted coding requests too. But changing the plan itself — priorities, scope, schedule — still goes through your contractor; two-way plan changes are on the roadmap.

Everything here arrives through your contractor — the invite link, the reports, the answers. If you don't have your link yet, ask them for your Mango invite — or request a seat yourself and we'll bring them aboard together.

What does your overhead cost you?

Planning, status updates, invoicing, “am I on pace?” math — the hours you can't bill. Slide to your numbers; the math runs right here, nothing leaves the page.

Your hourly rate — $95 Active clients — 3 Overhead hours per week — 6

The overhead tax, monthly≈ $3,040/mo

$95/hr × 7.4 effective h/wk × 4.3 wk — time you worked but couldn't bill.

≈ 7.4 hrs/week — a working Tuesday, every week.

Mango carries the planning, the updates, the invoicing, and the busywork.

Mango carries this — request a seat Existing user? Sign in

🧪 Dogfooded daily Live

The product manages the business that builds it

Built and used daily by Matthew Kerns (iCodeMyBusiness) to run his own contracting business. Real aggregates from the live system, as of Jul 11, 2026:

≈966 hrstracked across 3,790 entries since May 13

7 clients+ personal time, each sealed in its own lane

2× dailySlack kickoff & shutdown threads since Jul 6

110+ toolslive on the connector, across 4 surfaces

🔒 Private beta

First access goes to applicants

We onboard a few contractors at a time — every seat gets the daily loop tuned to their business. The dashboard is closed for now; applying is open, and the best applications come from a conversation.

Client seats are open too. Mango sits between you and your contractor — approved updates and plain-English answers in the chat you already use. Tell us about your project and we'll onboard you together. Already working with a contractor on Mango? Skip the line — ask them for your invite link.

🥭 Chat with our discovery agent

Tell us about your use case in your own Claude — quick three questions, or as detailed as you'd like. Add the open connector and say “I want to apply to Mango.”

https://mango.icodemybusiness.com/mcp/apply

Claude → Settings → Connectors → Add custom connector → paste the URL. No account needed — the connector itself is open.

✉️ Or just leave your email

Every application is reviewed — you'll hear back within 2 business days, either way. Applications queue ahead of quick joins; no drip campaign. Clients are welcome to request a seat too — and if your contractor is already on Mango, you don't need one: just ask them for your invite link.

📖 Tool glossary

Every capability, every surface

One connector — mango — reachable from four places. The matrix shows what works where today; the tables list every tool with its implementation status, and expected launch months for what's coming this year.

Capability	🌐 Web app	✳️ Claude	💬 Slack	📱 WhatsApp
🧭 Morning brief & ranked day	✅	✅	✅	🔜
🗓 Planning cadence — kickoff · shutdown · weekly	—	—	✅	—
🎯 Objectives (Rocks) & pace	✅	✅	✅	🔜
💵 Time, income & projections	✅	✅	✅	🔜
📄 Invoices & cash forecast	✅	✅	✅	—
📊 KPI flags — stale PRs, income pace	✅	✅	✅	—
🤖 Autonomous coding → reviewed PR	✅	✅	✅	—
🧵 Steer a live coding session	✅	✅	✅	—
✍️ Weekly client report drafts	✅	✅	✅	—
📋 Sprint workbook ingest	✅	✅	—	—
🤝 Proposals & estimates	✅	✅	—	—
🧠 Company Brain — durable memories	✅	✅	🔜	—
👂 Listening — context capture per client	—	—	✅	✅
👥 Client Q&A — allow-listed, scoped to their project	—	✅	✅	🔜
🪄 Prospect demos, built from a sentence	—	✅	🔜	—

✅ live today · 🔜 on the roadmap · — not on this surface. Slack access is per-person, per-channel, deny-by-default.

🥭 mango — contractor side You run the work Browse all 110+ tools ▾

You run the work The full operating surface on mango.icodemybusiness.com — 110+ tools, grouped by what they do (the coding-practices guide now lives here too).

Tool	What it does	Status
Onboarding & meta
`mango_capabilities`	Self-describe the connector: every tool, its purpose, and read/write kind.	✅ Live
`get_onboarding_status`	Check whether onboarding is done and which role was chosen.	✅ Live
`set_role`	Record the onboarding role (contractor or client).	✅ Live
Daily plan
`get_morning_brief`	Today's ranked cross-client to-do — the highest-leverage open items.	✅ Live
`get_daily_todo`	Live cross-client to-do for right now, grouped per client with sources.	✅ Live
`get_yesterday_snapshot`	Yesterday's hours, entries, avg duration, context switches, category split.	✅ Live
Objectives & plan
`get_rocks_status`	A client's objectives tree: each rock's % complete, tasks, and roll-up.	✅ Live
`get_objective_hours`	Hours logged toward a client's objectives over the last N days.	✅ Live
`get_objective_week`	This week's per-objective hours vs the Sunday-locked target + on-pace flags.	✅ Live
`get_project_todos`	A client's open objective tasks, each flagged for autonomous-run eligibility.	✅ Live
`prepare_project_todos`	Stage selected project-todos as a state-sync proposal for review.	✅ Live
`get_contract`	A client's operating contract: covenant, cadence, fee terms, versions.	✅ Live
`get_horizon_plan`	Long-horizon plan: objectives per horizon, month through ten-year.	✅ Live
`set_horizon_item`	Add or update a long-horizon objective.	✅ Live
Time & money
`get_time_summary`	Aggregate hours and earnings over a window, optionally per client.	✅ Live
`get_invoice_status`	Current biweekly invoice periods for paid clients (hours, earned, days left).	✅ Live
`get_projections`	Revenue run-rate plus scenario projections at various hourly mixes.	✅ Live
Context — Slack · Fathom · GitHub · local
`get_recent_context`	Latest ingested context, newest-first (Slack, Fathom, GitHub, email).	✅ Live
`search_external_context`	Search ingested context across GitHub, Slack, Fathom, and the archive.	✅ Live
`get_meeting_recap`	Recent Fathom meeting recaps for a client, attendee-scoped.	✅ Live
`get_local_work`	Recent local Claude Code sessions plus the local runner's code runs.	✅ Live
Company brain (memory)
`read_memories`	Recall durable business knowledge — the company Business Handbook.	✅ Live
`write_memories`	Save durable business knowledge into the Business Handbook.	✅ Live
Connections
`list_connections`	List connected accounts by provider, with client binding and status.	✅ Live
`add_connection`	Add a new account under a provider.	✅ Live
`reauth_connection`	Replace an account's credentials, keeping its record and binding.	✅ Live
`rebind_connection`	Re-point an account to feed a different client.	✅ Live
`test_connection`	Probe one account's stored credentials for connectivity.	✅ Live
`remove_connection`	Delete an account's credentials and its connection record.	✅ Live
State sync (local → Mango)
`preview_state_sync`	Stage a hand-crafted project-state update (advanced).	✅ Live
`get_state_sync`	Fetch a staged state-sync proposal (input + diff).	✅ Live
`apply_state_sync`	Commit a staged state-sync proposal after reviewing the diff.	✅ Live
`discard_state_sync`	Discard a staged state-sync proposal without applying it.	✅ Live
`list_state_sync`	List recent state-sync proposals by status.	✅ Live
Workbook ingest
`ingest_workbook_get`	Fetch a staged workbook-ingest proposal (plan + diff).	✅ Live
`ingest_workbook_apply`	Apply a staged workbook ingest onto the sprint plan.	✅ Live
`ingest_workbook_discard`	Discard a staged workbook ingest.	✅ Live
`ingest_workbook_list`	List recent workbook-ingest proposals by status.	✅ Live
Proposals & offers
`proposal_start`	Start a client-facing proposal/offer (tiered-options workbook).	✅ Live
`proposal_get`	Fetch a proposal: intake, options, and status.	✅ Live
`proposal_update`	Update a proposal's intake, options, or title.	✅ Live
`proposal_generate`	Gate and mark a proposal generated, returning the file name.	✅ Live
`proposal_list`	List recent proposals by status.	✅ Live
Autonomous coding & runs
`code_run_status`	Lifecycle and verification state of one Mango code run.	✅ Live
`code_runner_status`	Whether code execution is available on this instance, and why.	✅ Live
`list_code_runs`	List autonomous coding runs, newest first.	✅ Live
`list_buildable_features`	Partially-built features worth an autonomous run, per worktree.	✅ Live
`get_overnight_digest`	Morning digest of overnight autonomous activity.	✅ Live
`schedule_run`	Schedule an autonomous run for a task or objective.	✅ Live
`list_scheduled_runs`	List scheduled autonomous runs.	✅ Live
`update_scheduled_run`	Update a scheduled run.	✅ Live
`cancel_scheduled_run`	Delete a scheduled run.	✅ Live
`set_autonomous_target`	Set the autonomous-share target (0–100%).	✅ Live
Compute & cost
`get_compute_overview`	Manual (Clockify) vs autonomous (runner) compute over a window.	✅ Live
`get_compute_capacity`	Free run slots, concurrency, remaining budget, and autonomous share.	✅ Live
`list_cost_budgets`	List active LLM-spend caps.	✅ Live
`set_cost_budget`	Create an LLM-spend cap governing autonomous-run usage.	✅ Live
`update_cost_budget`	Update a cost budget.	✅ Live
`delete_cost_budget`	Delete a cost budget.	✅ Live
Session control — steer live engine runs
`session_status`	State of a live coding session: goal, loop, queued messages.	✅ Live
`session_send_message`	Inject a message into a running coding session's next turn.	✅ Live
`session_set_goal` / `session_clear_goal`	Pin or clear a goal prompt the session re-checks each turn.	✅ Live
`session_set_loop` / `session_clear_loop`	Set or clear a recurring loop prompt for the session.	✅ Live
Research projects & workspace
`setup_research_project`	Charter an overnight research project against a pinned repo.	✅ Live
`list_vps_workspace`	List the repos synced into the engine's workspace.	✅ Live
Repo & project context
`list_projects` / `get_project_context`	Projects Mango knows, and the working context for one.	✅ Live
`list_repo_files` / `get_repo_file`	Browse and read files from a connected repository.	✅ Live
`get_planning_repo_pulse`	Recent commits and PR activity for the planning repo.	✅ Live
`get_focus_projects` / `get_my_updates`	Current focus set and the updates drafted for you.	✅ Live
Clockify
`list_clockify_projects` / `list_clockify_tasks`	Read raw Clockify projects and tasks.	✅ Live
`create_clockify_project` / `create_clockify_task`	Create Clockify projects/tasks on explicit ask.	✅ Live
Estimation & demos
`project_estimate`	PERT estimate from a project intake.	✅ Live
`demo_create` / `demo_status` / `demo_revise`	Build, track, and revise a from-scratch prospect demo.	✅ Live · consent-gated
`demo_publish` / `demo_unpublish` / `demo_list`	Consent-gated publishing of demos to a live URL.	✅ Live · consent-gated
`demo_grant_access` / `demo_revoke_access` / `demo_list_grants`	Per-prospect access grants for private previews.	✅ Live
Client invites
`get_my_invite` / `accept_invite` / `decline_invite`	The invite flow that binds a client to their shared reports.	✅ Live
BMAD studio — product-planning agents
`bmad_list_agents` / `bmad_run_agent`	Browse and run the ~76-agent BMAD library (brainstorm → PRD → architecture).	✅ Live
`bmad_autodev` / `bmad_brainstorm` / `bmad_create_prd`	Named shortcuts for the most-used agents.	✅ Live
`bmad_save_artifact` / `bmad_get_artifact` / `bmad_list_artifacts`	Persist and retrieve the artifacts agents produce, filed per client.	✅ Live
`bmad_find_artifacts` / `bmad_list_client_artifacts` / `bmad_compare_artifacts`	Search, browse, and diff artifacts across clients.	✅ Live
Coding-practices guide (formerly the separate `mango-tools` server)
`guide_list` / `guide_search` / `guide_read`	Browse, search, and read the software best-practices guides.	✅ Live
`guide_checklist` / `guide_scaffold_agents_md` / `guide_validate_flag_registry`	Ready-made checklists, AGENTS.md scaffolds, flag-registry validation.	✅ Live
`architecture_guidance` / `reorganization_guidance`	Design and refactoring guidance grounded in the guide corpus.	✅ Live
Goal-prompt creator — the gauntlet method for agentic coding runs
`goal_prompt_guide`	The codified gauntlet method: paired artifacts (spec + build) attack each other through three persistent critics until neither can break the other. Methodology, skeleton, worked example.	✅ Live
`goal_prompt_validate`	Readiness gate on a draft goal prompt: char cap, section structure, critic loop, HALT allowance. Iterate until it passes.	✅ Live
On the roadmap — expected this year
`whatsapp_replies`	@Mango answers in WhatsApp the way it does in Slack (per-identity routing).	🔜 expected Aug 2026
`slack_company_brain`	Company-Brain memories + scheduling inside the Slack assistant's toolset.	🔜 expected Aug 2026
`slack_demo_spinup`	"@Mango demo for prospect" builds and links a live demo in-thread.	🔜 expected Sep 2026
`seat_emails`	Automated waitlist emails — confirmation and "your seat is open."	🔜 expected Sep 2026
`gmail_zoho_connections`	Email as a context source, per client, like Slack and Fathom today.	🔜 expected Oct 2026
`client_two_way`	Clients request plan changes through their own chat (contractor approves).	🔜 expected Nov 2026

🥭 mango — client side Read-only · authorized Browse all client tools ▾

Read-only · authorized What a client sees through their own AI — only the snapshots you authorize, scoped to their engagement. Live data is never exposed.

Tool	What it does	Status
`mango_weekly_report`	The latest contractor-authorized weekly update: hours and billed amounts by day and project, plus the note.	✅ Live
`mango_daily_update`	The latest contractor-authorized daily update: time entries plus the contractor's note.	✅ Live
`mango_pace_status`	Is the contractor on pace this week? Per-objective % complete and an on-pace flag.	✅ Live
`mango_invoices_list`	Invoices for this engagement (filter paid · pending · overdue · all).	✅ Live
`mango_overdue_alert`	Unpaid invoices past their 30-day due date, with amount and days overdue.	✅ Live
`mango_cash_forecast`	Your expected contractor cost this month — what's coming due vs already paid vs pending, from the work and terms your contractor has logged.	✅ Live

In the loop —without ever asking.

Your day was plannedbefore you woke up.