151. Operations Templates

Operations are how a startup remembers, decides, and improves while moving fast. These templates are intentionally simple: they create rhythm without turning the company into a paperwork machine.

Use them when work is starting to fall between people, decisions keep repeating, or the founder is carrying too much context in their head.

Weekly review

A weekly review should surface reality early. It is not a performance theatre document.

Section	Prompt
Week of	Date range.
Company priority	The one priority that mattered most this week.
Wins	What moved forward? Include customer, product, sales, hiring, finance, and ops wins.
Misses	What did not happen? Be specific, not vague.
Metrics	3-7 operating metrics with current value, previous value, and comment.
Customer signals	Calls, complaints, renewals, churn reasons, usage patterns, referrals.
Decisions made	Important decisions and why. Link to decision log if needed.
Blockers	What is stuck, who owns it, and what decision is needed.
Next week	Top 3 priorities, each with an owner.

Founder closing question:

If we only fix one thing next week, what creates the most leverage?

Founder operating dashboard

Use this when the company feels busy but unclear.

Area	Metric or signal	Why it matters	Owner
Customer learning	Useful customer conversations this week	Keeps reality close.
Product	Users/accounts reaching first value	Shows whether building creates adoption.
Revenue	New revenue, pipeline quality, collections	Separates activity from business progress.
Retention	Repeat usage, renewals, churn reasons	Shows whether value lasts.
Cash	Burn, runway, large upcoming payments	Protects survival.
Hiring/team	Open roles, performance issues, morale risks	Avoids hidden people debt.
Decisions	Important open decisions older than 7 days	Prevents drift.

Do not put 40 metrics here. The point is to force a weekly conversation about the few signals that can change founder behavior.

Monthly metrics report

Use the monthly report to separate motion from progress.

Metric	Current month	Previous month	Target	Comment	Owner
Revenue or active usage				What changed and why?
Pipeline or leads				Quality, source, conversion.
Activation or onboarding				Where users/customers get stuck.
Retention or repeat use				Churn, repeats, expansion, engagement.
Gross margin or delivery cost				Cost to serve customers.
Burn and runway				Cash discipline and runway risk.
Hiring/team				Open roles, performance, morale.

Narrative sections:

Section	Prompt
What improved	The strongest real progress this month.
What worsened	Metrics or signals that need attention.
What surprised us	Anything that changed your view of customer, product, market, or team.
Decisions needed	What the leadership team/founders must decide.
Next month focus	The few priorities that matter most.

Monthly close checklist

Use this at the end of each month, even before the company has a finance team.

Check	Owner	Done?
Revenue, invoices, and collections reviewed
Burn and runway updated
Large upcoming payments listed
Hiring commitments and contractor costs reviewed
Customer churn, complaints, and expansion signals summarized
Product usage or delivery metrics reviewed
Important decisions logged
Next month’s top 3 priorities chosen

This is not a finance ritual. It is a founder reality check. A startup can look energetic while cash, retention, or delivery quality quietly moves the wrong way.

Decision log

Most startup confusion comes from forgotten decisions. A decision log keeps context alive.

Field	Prompt
Decision	What did we decide?
Date	When?
Owner	Who is accountable for the outcome?
Context	What situation forced the decision?
Options considered	What real alternatives were discussed?
Reasoning	Why this option? What tradeoff did we accept?
Expected outcome	What should improve?
Review date	When will we check if it worked?
Reversal trigger	What evidence would make us change course?

Use especially for pricing, hiring, product direction, fundraising, pivots, major customer commitments, and cost cuts.

Open decision tracker

Use this when founders keep saying “we need to decide that” but nothing closes.

Decision needed	Owner	Options	Deadline	Cost of delay	Status
				Revenue / product / hiring / cash / morale / compliance	Open / decided / deferred

Decision hygiene:

• Every important decision has one owner.
• Every decision has a deadline or a reason to wait.
• A reversible decision should not consume weeks.
• An irreversible or expensive decision deserves written options.
• If the same decision returns three times, the original reasoning was unclear or the situation changed.

Founders often lose time not because they choose wrong, but because they leave too many choices half-open.

Meeting notes

Every meeting should produce a decision, a learning, or a next action.

Field	Prompt
Meeting	Name and date.
Purpose	Why did we meet?
Attendees	Who was present?
Context	What information matters before reading the notes?
Discussion summary	Important points, disagreements, customer facts, constraints.
Decisions	What was decided?
Action items	Owner, action, due date.
Open questions	What still needs clarification?

Action item format:

Owner	Action	Due date	Done?
Name	Specific verb-led task.	Date	Yes/No

Meeting operating rules

Use these rules as defaults until the company needs something more formal.

Rule	Why
Name the meeting purpose before it starts	Prevents status theatre.
Put metrics or written context first	Saves time and reduces storytelling bias.
Separate discussion from decision	Not every discussion deserves a decision today.
Assign one owner per action	Shared ownership usually means no ownership.
End with the next visible artifact	Doc, shipped change, customer call, decision, invoice, candidate feedback, etc.

Cancel any recurring meeting that does not regularly produce decisions, learning, or coordination that could not happen async.

Project brief

Use this before starting work that requires more than one person or more than one week.

Section	Prompt
Project name	Clear, boring name.
Problem	What problem are we solving?
Customer/internal user	Who benefits?
Goal	What outcome should change?
Non-goals	What are we explicitly not doing?
Scope	What is included in version one?
Milestones	Key dates or checkpoints.
Owner	One accountable person.
Stakeholders	Who needs to be consulted or informed?
Risks	What could delay or weaken the project?
Success metric	How will we know this worked?

RACI-lite responsibility map

Use this when work crosses founders, employees, contractors, agencies, or advisors.

Workstream	Responsible	Approver	Consulted	Informed
Product release
Key customer onboarding
Fundraising process
Hiring pipeline
Finance/reporting
Compliance/admin

Definitions:

Role	Meaning
Responsible	Does the work.
Approver	Makes the final call.
Consulted	Gives input before the decision.
Informed	Needs to know after the decision.

This prevents two common startup problems: everyone assuming the founder owns everything, and multiple people thinking they have final say.

Incident report

Incidents are learning events. Do not turn them into blame sessions.

Field	Prompt
Incident	What happened?
Date/time	When did it start and end?
Impact	Who was affected and how badly?
Detection	How did we find out?
Timeline	Key events in order.
Root cause	What actually caused it? If unknown, say unknown.
Contributing factors	Process, tooling, staffing, communication, vendor, data, or product issues.
Resolution	What fixed it?
Customer communication	What was communicated and when?
Follow-up actions	Owner, action, due date.

Severity guide:

Severity	Meaning
Sev 1	Major customer/business impact, urgent leadership attention needed.
Sev 2	Significant impact, needs quick fix and follow-up.
Sev 3	Limited impact, still worth learning from.

Customer issue tracker

Use this when support, onboarding, and product feedback are scattered across WhatsApp, email, calls, and memory.

Customer/account	Issue	Severity	Source	Owner	Next update	Root cause	Product/action
		Critical / high / medium / low	WhatsApp / email / call / ticket / sales			Product / training / expectation / bug / billing / ops

Review this weekly. If three customers face the same issue, it is no longer “support”; it is product, onboarding, documentation, or positioning debt.

SOP

An SOP should let a competent person do repeatable work without asking the founder every time.

Section	Prompt
Process name	What is this SOP for?
Owner	Who maintains it?
Purpose	Why this process exists.
When to use it	Trigger or frequency.
Inputs needed	Data, access, tools, approvals.
Step-by-step process	Numbered steps with enough detail to execute.
Quality checks	How to know the work is correct.
Escalation	When to ask for help and whom to contact.
Output	What should exist when done?
Last updated	Date and reviewer.

Keep SOPs short. If the process changes every week, document principles and checklists instead of pretending it is stable.

Vendor and tool inventory

Founders often discover tool chaos only during fundraising diligence, security review, or employee exits.

Tool/vendor	Purpose	Owner	Monthly/annual cost	Access level	Renewal date	Risk
				Admin / editor / viewer / API / payment		Low / medium / high

Review for:

• Former employees or contractors with access.
• Founder-only accounts that should have shared recovery.
• Unused paid tools.
• Customer data stored in risky places.
• Critical tools without backup or export.
• Renewal surprises that hurt cash planning.

This is boring work, which is exactly why it saves startups during messy moments.

Company wiki structure

Start with a small wiki. The goal is fast access to truth, not a perfect knowledge base.

Section	What belongs here
Start here	Company mission, current priorities, operating principles, important links.
Customers	ICP, personas, customer notes, case studies, objections, support themes.
Product	Roadmap, release notes, PRDs, analytics, bugs, design decisions.
Sales/GTM	Positioning, messaging, outreach, pipeline process, pricing, proposals.
Operations	Weekly reviews, meeting notes, decision log, SOPs, vendor list.
Finance	Burn, runway, budget, invoices, collections, reporting rhythm.
Hiring/team	Roles, hiring process, onboarding, benefits, performance expectations.
Legal/compliance	Company docs, contracts, policy links, compliance calendar, advisor contacts.

Wiki rule:

If a founder answers the same operational question three times, the answer should become a wiki page or SOP.

Minimum operating system by stage

Do not install a large-company operating system into a tiny startup. Add operating artifacts only when they reduce confusion, improve decisions, or protect trust.

Stage	Minimum artifacts	What they prevent
Solo founder or idea stage	Weekly review, decision log, prospect/customer notes.	Wandering, forgotten decisions, fake progress.
Co-founder stage	Weekly review, founder operating dashboard, open decision tracker.	Silent disagreement, duplicated work, unclear ownership.
First customers	Customer issue tracker, project brief, monthly metrics report.	Lost commitments, reactive delivery, weak learning loops.
First hires	Meeting notes, RACI-lite map, onboarding docs, company wiki structure.	New people depending only on founder memory.
Scaling team	SOPs, incident reports, vendor/tool inventory, monthly close checklist.	Repeat mistakes, tool sprawl, operational surprises.

A useful operating system has a rhythm:

• Weekly: priorities, decisions, customer issues, cash, blockers.
• Monthly: metrics, finance close, hiring plan, major risks.
• Quarterly: strategy, team structure, product and GTM bets, capital needs.

The founder’s job is to keep the system lightweight and honest. If the team updates templates but decisions do not improve, the system is decorative. If decisions improve but documentation is imperfect, the system is doing its job.

Operating artifact quality bar

Every operating artifact should pass this test.

Test	Good artifact	Bad artifact
Owner	One named person owns it.	”Team” owns it, so nobody does.
Date	Last updated date is visible.	Nobody knows if it is current.
Decision link	It supports a decision or action.	It exists because someone asked for documentation.
Evidence	Numbers, customer examples, incidents, or facts are included.	It is mostly opinions and status language.
Next action	The next step is explicit.	The reader must infer what to do.
Review rhythm	It has a review cadence.	It is created once and forgotten.

Use this cleanup rule once a month:

• Keep artifacts that drive decisions.
• Merge artifacts that duplicate each other.
• Archive artifacts that are stale.
• Delete artifacts that nobody uses.

The danger in operations is not only chaos. It is also process theater: meetings, dashboards, and documents that make the company feel managed while the real bottlenecks remain untouched.

Copy-paste weekly operating packet

Use this as the weekly operating document for a small founding team.

Week of:

Main company objective:

Top customer truth:

Top revenue / sales truth:

Top product / delivery truth:

Top cash truth:

One decision we must make:

One thing we will stop doing:

Founder focus:

Scoreboard:

Metric	Last week	This week	Change	Interpretation
Customer conversations
Qualified pipeline / leads
Revenue / committed revenue
Activation / usage
Cash runway
Product delivery

Decision log:

Decision	Owner	Why now	Revisit date

Commitments:

Commitment	Owner	Due date	Status	Next action

Weekly operating documents should be short enough to actually use. If the team cannot update it in 30 minutes, it will become theatre.

30-Day Operating System Install Plan

Use this when the startup has grown beyond founder memory but does not yet need heavy process. The goal is to install just enough operating rhythm to reduce chaos.

Week	Install	Founder action	Success signal
1	Weekly review and open decision tracker	Run one honest review. Write every open decision with owner, deadline, and cost of delay.	The team knows the top 3 priorities and the decisions blocking progress.
2	Customer issue tracker and decision log	Capture repeated customer issues and record the reasoning behind important calls.	Repeated issues stop living only in WhatsApp, calls, and founder memory.
3	Monthly metrics report and close checklist	Pick 5-7 metrics, update runway/burn, review collections, and list commitments.	Founders can see cash, customer, product, and revenue reality on one page.
4	RACI-lite and wiki structure	Clarify ownership for recurring work and create the first company knowledge map.	New work has a clear owner, approver, and place where context lives.

Do not install all templates at once. Pick the one that removes the most confusion this week. A useful operating system should make decisions faster, customer promises clearer, and founder attention more focused.

Operating system failure signals

Pause and simplify if:

• Meetings increase but decisions do not.
• People update templates without reading them.
• Metrics are reported but never change behavior.
• Founders still answer the same operational question repeatedly.
• The team cannot explain the top company priority without checking a doc.

Operations should create leverage, not ceremony.

Copy-paste operating debt review

Use this once a month when the company feels slower, noisier, or more dependent on founder memory.

Month:

Where did work get stuck repeatedly?

Which decision returned more than once?

Which customer promise was hard to track?

Which tool, vendor, or access issue created risk?

Which founder-only task should become a checklist, SOP, hire, or refusal?

Which recurring meeting or document did not change behavior?

What will we simplify next month?

Operating debt table:

Debt	Cost	Owner	Fix	Review date
Repeated customer onboarding confusion	Slower activation, founder interruptions		Checklist / doc / product fix / training
Open decisions without owners	Team waits or duplicates work		Decision log and deadline
Tool access scattered	Security and onboarding risk		Vendor/tool inventory cleanup

Treat operating debt like product debt: not every issue deserves immediate work, but repeated friction should be made visible.

Founder handoff template

Use this when the founder delegates work to an employee, contractor, agency, advisor, or co-founder.

Field	Prompt
Work being handed off
Why this work matters	Customer, revenue, product, cash, hiring, compliance, or founder focus.
Owner	One accountable person.
Decision rights	What can they decide without asking?
Constraints	Budget, timeline, brand, customer promise, legal/security, quality bar.
Inputs	Docs, links, customer context, data, examples, access.
Output	What should exist when done?
Check-in rhythm	Daily, weekly, milestone-based, or async.
Escalation	What should be raised immediately?
Done standard	How will the founder know this is complete?

Bad handoff:

Can you take care of onboarding?

Better handoff:

Please own onboarding for the next 5 pilot customers. Success means each customer reaches first value within 7 days, support issues are logged, and repeated setup questions become a checklist by Friday.

Delegation fails when the founder transfers tasks but not context, decision rights, or quality standards.

Operating review red flags

Add these red flags to weekly or monthly reviews.

Red flag	Why it matters	Founder move
Same blocker appears three weeks in a row	It is not a blocker anymore; it is an unresolved decision or capacity problem.	Assign decision owner and final date.
Metrics are reported but never discussed	Dashboard is becoming decoration.	Remove or connect metric to action.
Customers ask the same question repeatedly	Onboarding, product, sales, or documentation is weak.	Convert into FAQ, product fix, or sales scope change.
Founder answers every operational question	Company is not learning without founder.	Write SOP, appoint owner, or refuse low-value work.
Meeting ends without owner/date	Conversation replaced execution.	Re-run the close: owner, action, date.
Tool costs or access surprises appear	Vendor and security hygiene are weak.	Update inventory and access review.

These red flags are not signs that the company needs heavy process. They are signs that one small operating artifact may save a lot of founder attention.

Related chapters

• Company Operating System
• Decision Making
• Startup Metrics Basics