Teach Marg your business

What you'll get

A business profile that every team reads before it touches your request. That profile is the whole difference between advice for "a startup" and advice for yours. Building it takes five minutes once, and keeping it current takes a single line whenever something changes.

The steps

1. Build the profile once.

/marg:onboard

Marg asks seven questions, one at a time: what you are building, your stage, B2B or B2C, revenue range, team size, biggest challenge, and competitive landscape. The answers live in a profile file in your working folder, where every routing decision reads them. You ran this in chapter 3, so the thing to know now is that you can rerun it any time and it rewrites the profile clean.

2. Update it as the business moves. A startup changes weekly, and re-answering seven questions every time would be absurd, so you drop a one-line note instead:

/marg:btw we crossed 50k MRR last week

/marg:btw hired two engineers, team is now 9

/marg:btw priority is now enterprise deals, not self-serve

3. Let the note find its home. Marg reads each note and files it where it belongs: revenue mentions update your revenue range, headcount mentions update team size, priority shifts move to the top of your priorities, and everything else lands in session memory for context. No team spawns, nothing runs, and you are back to what you were doing in seconds.

What comes back

Each note gets a one-line confirmation of what was recorded and where. The real return is invisible and later: a pricing question answered for a 9-person company at 50k MRR chasing enterprise, with none of that repeated by you, because the profile already carried it.

Variations

• Started with thin answers? Rerun /marg:onboard after your first week. The second pass is always sharper, because by then you have seen what the teams actually do with the context and you describe it better.
• Sensitive details: the profile is a file in your working folder, on your repo or machine, not on anyone's server. Share what you would share with a senior hire on day one.

If something goes wrong

• A note filed as the wrong type: rephrase with the signal made explicit ("revenue:", "team size is now") and resend, since the latest note wins.
• The profile feels stale after a pivot: do not patch it line by line. Rerun /marg:onboard and answer fresh, because a clean rewrite beats a corrected history every time.
• You typed /marg:btw with nothing after it: Marg returns usage rather than guessing. Add the note and resend.