The complete A working reference for planning, launching and operating a consumer brand. Every requirement includes its purpose, actions, record fields and review standard.
This reference contains no customer or project data. Use the interactive atlas for saved records, status tracking, financial checks and project exports. Examples are illustrative; business identity, fees other than the stated consultation fee, policies and credentials must be confirmed by the responsible owner. The local atlas does not provide authenticated cloud collaboration.
Open the interactive operating plan →
01 / Consultation 02 / Booking and terms 03 / Business and commercial terms 04 / Founder and category fit 05 / Customer evidence 06 / Product and suppliers 07 / Economics and cash 08 / Brand and purchase experience 09 / Sales and repeat purchases 10 / Delivery and governance Consultation Define the discussion, preparation and next decisions.
REQUIREMENT 01 / 100 · Rishi / engagement owner
Consultation offer The visitor should understand the service before opening WhatsApp.
Required actions Show ₹2,000 and 60 minutes together with Rishi’s name. Use one consistent description on the home, finance and delivery pages. Describe the next step as a booking request; payment and confirmation follow separately. Review standard
Working record Page / placement Offer wording Last review and issue found Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The existing CTA opens +91 70240 15382 with a draft request; it does not make a payment.
REQUIREMENT 02 / 100 · Rishi / engagement owner
Consultation placement Make help available at the point where a founder needs a decision.
Required actions Keep the home CTA visible beside the introduction. Place finance help beside the financial model and delivery help beside the execution scope. Check the button on mobile and confirm that its message describes the relevant discussion. Review standard
Working record Placement Customer question at this point Destination and mobile check Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A founder reviewing cash requirements reaches a finance-focused consultation request.
REQUIREMENT 03 / 100 · Rishi / engagement owner
Decisions from the session Set a useful outcome without promising a complete business plan in one hour.
Required actions Identify the most important decision before the meeting. Review the evidence available and distinguish conclusions from assumptions. Agree the next three actions, their owners and any separate work required. Review standard
Working record Primary decision Evidence available Expected output and exclusions Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Choose whether to test a two-product routine before committing to opening inventory.
REQUIREMENT 04 / 100 · Rishi / engagement owner
60-minute agenda Use the discussion time for decisions instead of collecting basic background.
Required actions Reserve 0–10 minutes for context and constraints; 10–25 for the buyer and product. Use 25–45 for price, costs, cash and route to market. Use 45–60 for risks, open questions and next actions; adjust the draft agenda to the actual need. Review standard
Working record Session objective Agenda changes Decisions reserved for the final 15 minutes Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A running brand may spend the middle block on returns and contribution rather than category selection.
REQUIREMENT 05 / 100 · Rishi / engagement owner
Founder suitability Clarify what can be discussed at different stages of a business.
Required actions For an idea-stage founder, review the buyer, category, capital and validation route. For an existing business, review the D2C offer and operational gaps. For an operating brand, use actual channel, product and cash records; identify specialist matters separately. Review standard
Working record Founder stage Current challenge Information needed for a useful session Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An operating brand brings retained sales and spend by channel, not only its revenue screenshot.
REQUIREMENT 06 / 100 · Rishi / engagement owner
Consultation scope Separate discussion from work that needs research, execution or specialist review.
Required actions Describe the session as a review of the information supplied. List exclusions such as supplier verification, formulation, legal opinions, campaign execution and a full financial build. Record any follow-on work in a separate scope with an owner, output and fee. Review standard
Working record Included discussion Excluded work Separate engagement required Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A supplier quote can be discussed; an audit or verified factory assessment is separately scoped.
REQUIREMENT 07 / 100 · Rishi / engagement owner
Pre-call questionnaire Collect enough context to prepare without requesting unnecessary personal data.
Required actions Ask for category, stage, available capital, intended launch date and up to three questions. Request an optional website or relevant document reference. Let the founder review the prepared message before choosing to send it on WhatsApp. Review standard
Working record Category and stage Available capital and launch timing Top three questions Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note “Skincare; idea stage; ₹40 lakh available; launch after product checks; need help selecting the first range.”
REQUIREMENT 08 / 100 · Rishi / engagement owner
Documents for review Use a stage-appropriate evidence pack rather than a generic upload request.
Required actions For a new brand, collect the brief, interview notes, sample observations and supplier quotations if available. For a running brand, add SKU costs, channel sales, returns, media spend and a dated cash summary. Remove passwords and unnecessary customer details; identify missing or outdated documents. Review standard
Working record Document and version Period / scope covered Missing information or redactions Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Share a summary of delivered and refunded orders by channel, not a full customer database.
REQUIREMENT 09 / 100 · Rishi / engagement owner
Written action note Make the discussion usable after the call.
Required actions Record the observations, evidence gaps and decisions actually made. Write three next actions with owners and dates. Agree separately whether a written note is included and its delivery timing before accepting payment. Review standard
Working record Observations and decisions Open questions Three actions with owner and date Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Action 1: obtain two comparable quotes; action 2: test price; action 3: update the cash case.
Related requirements: 03, 04, 07
REQUIREMENT 10 / 100 · Rishi / engagement owner
Options after consultation Provide a clear next step without implying that execution is compulsory.
Required actions Present independent implementation as a valid route. Describe a research study, launch plan or execution scope only when relevant. Define the output, approval gate and commercial terms before further work begins. Review standard
Working record Recommended route Deliverable and approval gate Commercial proposal reference Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A short demand study may precede any inventory commitment or execution retainer.
Booking and terms Record availability, payment, terms and communications.
REQUIREMENT 11 / 100 · Booking owner
Advisor introduction Publish a factual description of Rishi’s role and involvement.
Required actions Record relevant experience, the work personally handled and the limits of involvement. Attach evidence or permitted references for specific experience claims. Approve the final public biography before publishing it. Review standard
Working record Role and involvement Experience with supporting reference Approved biography version Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Rishi’s name is confirmed. Years of experience, client names and performance claims remain to be supplied.
REQUIREMENT 12 / 100 · Booking owner
Business contact details Give the founder a consistent way to contact the responsible person.
Required actions Use the supplied business WhatsApp number and identify the responsible owner. Add a business email only after it is provided and verified. Specify the purpose of each contact channel and an agreed response window. Review standard
Working record Contact channel and address Responsible person Purpose and response window Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note WhatsApp: +91 70240 15382. No business email has been supplied yet.
REQUIREMENT 13 / 100 · Booking owner
Payable amount and invoice basis Resolve the total amount before asking for payment.
Required actions Confirm whether the ₹2,000 quoted fee includes any applicable tax. Have the business or finance owner approve the invoice identity and tax treatment. Share the final payable total and payment reference before the founder proceeds. Review standard
Working record Quoted fee and tax basis Final payable total Approved invoice details Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The session fee is ₹2,000; tax inclusion has not been confirmed and must not be guessed.
Related requirements: 12, 21
REQUIREMENT 14 / 100 · Booking owner
Availability and meeting format Avoid treating a preferred time as an accepted appointment.
Required actions Ask for preferred dates and display the timezone as Asia/Kolkata. Record the confirmed date, start time, 60-minute duration and meeting format. Send the agreed meeting location or link; keep a calendar entry only after confirmation. Review standard
Working record Preferred dates Confirmed start and timezone Meeting format and link Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The calendar download in this workspace creates a manual reminder; it does not reserve availability.
REQUIREMENT 15 / 100 · Booking owner
Booking status Track the difference between a request and a confirmed session.
Required actions Use requested, slot proposed, awaiting payment, confirmed, completed or cancelled. Record who changed the state and the supporting communication reference. Confirm only when the agreed booking conditions are met. Review standard
Working record Booking reference Status and date Evidence of confirmation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A WhatsApp enquiry remains “Requested” until the slot and booking details are agreed.
Related requirements: 13, 14, 18, 19
REQUIREMENT 16 / 100 · Booking owner
Payment acknowledgement Keep payment records accurate and separate from payment processing.
Required actions Record amount received, date and a limited transaction reference. Match the receipt to the booking and approved invoice identity. Share an acknowledgement only after checking the payment with the actual provider or bank. Review standard
Working record Amount and date received Payment / receipt reference Booking match and reviewer Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A manually entered payment reference is a record, not proof that this website collected money.
REQUIREMENT 17 / 100 · Booking owner
Session reminders Make reminder responsibility and consent explicit.
Required actions Record the channel, joining details and a suitable reminder time. Assign manual reminders or configure the chosen booking provider. Check delivery or failure in the actual system and avoid sending duplicate reminders. Review standard
Working record Reminder time and channel Assigned sender / provider Sent or failed evidence Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An optional calendar file contains a local alert; WhatsApp reminders are not automated here.
REQUIREMENT 18 / 100 · Booking owner
Rescheduling terms Agree a process that is clear before the customer pays.
Required actions Decide the required notice, permitted changes and how a new slot is selected. Define what happens when the advisor needs to move the session. Approve and share the policy version before payment; do not invent a default notice period. Review standard
Working record Proposed notice and limits Advisor reschedule process Approved version and customer acknowledgement Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note “Notice period to be agreed” is an internal drafting field, not an accepted customer term.
REQUIREMENT 19 / 100 · Booking owner
Cancellation, no-show and refunds Prevent ambiguity about a missed or cancelled session.
Required actions Specify cancellation eligibility, no-show treatment and any exceptions. Define how a refund is requested, reviewed and processed through the payment route. Obtain qualified review where needed and retain the policy version accepted by the customer. Review standard
Working record Cancellation and no-show proposal Refund process and timing Approved policy / acknowledgement Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note No non-refundable policy or refund deadline has been assumed for this service.
REQUIREMENT 20 / 100 · Booking owner
Post-call communication Set a reasonable boundary for follow-up.
Required actions Agree whether clarifications are included, the channel and the time window. Identify the owner who responds and what requires a separate engagement. Record any promised note or document and its due date. Review standard
Working record Included follow-up Channel and response commitment Excluded work and escalation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A clarification on a discussed action can be distinguished from building a new financial model.
Business and commercial terms Make capability, evidence, fees and ownership reviewable.
REQUIREMENT 21 / 100 · Business owner
Business identity Use consistent details across the site, proposal and invoice.
Required actions Record the trading name, legal entity where applicable and authorised signatory. Have the business owner verify invoice and contact details. Compare the approved details across all customer-facing documents. Review standard
Working record Trading / legal identity Invoice and signatory details Approved document references Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Brandlyhumann is the brand name; legal entity and invoicing details remain to be confirmed.
REQUIREMENT 22 / 100 · Business owner
Verified case studies Show evidence of actual work with enough context to interpret it.
Required actions Record starting conditions, scope, period, spend and the definition of the outcome. Separate contribution from factors outside the engagement and include material limitations. Obtain permission for identifiable clients, documents and results. Review standard
Working record Starting position and scope Period, spend and measured result Evidence, limitations and publication permission Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Routine No.01 is an illustrative project and cannot be relabelled as a real client result.
Related requirements: 23
REQUIREMENT 23 / 100 · Business owner
Work samples Let a founder inspect the quality of the deliverables.
Required actions Select a product brief, quote comparison, cost model and weekly report. Remove confidential information and retain the scope and version context. Label fictional examples as examples and obtain permission for real client material. Review standard
Working record Sample and version Context / what it demonstrates Permission and redaction review Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A blank purchase-order checklist demonstrates structure, not a verified supplier relationship.
REQUIREMENT 24 / 100 · Business owner
Team and responsibilities Show who is accountable for each part of the work.
Required actions Name confirmed team members and their actual roles. Distinguish employees, independent specialists and unappointed roles. Record involvement, capacity, decision rights and the escalation owner. Review standard
Working record Name and confirmed relationship Responsibility and availability Evidence and escalation owner Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note “Regulatory reviewer to appoint” remains a gap until a qualified person accepts the scope.
REQUIREMENT 25 / 100 · Business owner
Capability boundaries Clarify what the business delivers directly and what needs another party.
Required actions Map each deliverable to in-house work, a confirmed partner or a specialist to appoint. Verify access and capacity before making a delivery commitment. Identify the founder’s obligations and dependencies that affect the schedule. Review standard
Working record Capability and delivery route Confirmed provider and capacity Dependencies and exclusions Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A supplier introduction does not automatically include factory verification or product release approval.
REQUIREMENT 26 / 100 · Business owner
Deliverables catalogue Make the promised work inspectable and measurable.
Required actions Specify the output, format, level of detail and included revisions. Name the source inputs, delivery date and acceptance criteria. Identify ongoing services separately from one-time documents. Review standard
Working record Deliverable and format Inputs, revisions and due date Acceptance standard Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A supplier comparison includes like-for-like landed costs, MOQ, lead time, terms and unresolved checks.
REQUIREMENT 27 / 100 · Business owner
Execution fees and stages Show the commercial commitment before work begins.
Required actions List fixed fees, recurring fees and any variable fee basis separately. Tie billing stages to agreed dates or accepted deliverables. Record taxes, payment terms, revision limits and the treatment of scope changes. Review standard
Working record Fee basis and amount Billing trigger and due date Proposal version and inclusions Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The ₹2,000 consultation fee is confirmed; execution pricing has not been supplied.
Related requirements: 26, 28, 29, 30
REQUIREMENT 28 / 100 · Business owner
External expenditure Prevent service fees from hiding the cost of running the brand.
Required actions List product, packaging, tests, inventory, media, software, logistics and specialist costs. State who contracts, pays and approves each supplier. Separate quotes, estimates and contingencies; include payment dates in cash planning. Review standard
Working record Expense and estimate / quote Contracting and paying party Approval limit and payment date Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Inventory deposits and advertising spend remain in the brand cash plan even if coordinated by a studio.
REQUIREMENT 29 / 100 · Business owner
Commissions and markups Make commercial incentives visible before a recommendation is accepted.
Required actions Record referral fees, commissions, procurement markups or other benefits where they exist. State the payer, basis and potential effect on the recommendation. Disclose the arrangement before commitment and retain acknowledgement. Review standard
Working record Arrangement or explicit none Payer and calculation basis Disclosure and acknowledgement Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Do not state “no commissions” unless the business owner has verified that position.
REQUIREMENT 30 / 100 · Business owner
Ownership and access Protect the brand’s ability to operate independently.
Required actions Record ownership of the domain, artwork, formula or design rights, tooling, store and data. Define licences, transfer conditions and third-party restrictions in the agreement. Use named account access and founder-controlled recovery; store no passwords in this atlas. Review standard
Working record Asset and ownership / licence Access and recovery owner Transfer conditions and agreement Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Creator footage may be licensed for a limited period even when the brand owns its website.
Founder and category fit Match available cash, operating capacity and the launch scope.
REQUIREMENT 31 / 100 · Founder
Starting-stage assessment Begin with the current evidence and constraints.
Required actions Record whether the business is exploring, validating, preparing launch or already selling. Identify completed work, existing obligations and unresolved decisions. Prioritise the next approval gate instead of restarting every workstream. Review standard
Working record Current stage Completed work and obligations Next decision and missing evidence Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An existing retailer may have supply access but still need D2C unit costs and fulfilment tests.
REQUIREMENT 32 / 100 · Founder
Available capital Distinguish willingness to invest from usable cash.
Required actions Record cash available now, later committed funding and uncertain funding separately. Deduct existing business commitments and protect the agreed reserve. Link dated funding availability to supplier and launch payments. Review standard
Working record Available now Later funding amount, date and certainty Existing commitments and protected reserve Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A ₹50 lakh intention with ₹20 lakh available now cannot fund an immediate ₹35 lakh commitment.
REQUIREMENT 33 / 100 · Founder
Founder operating involvement Match the work plan to time the founder can actually provide.
Required actions Record weekly availability and which approvals require the founder. Allocate preparation, supplier review, content and commercial decisions. Identify coverage for absences and delays in decision-making. Review standard
Working record Weekly time available Responsibilities retained Backup and approval turnaround Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A two-hour weekly review cannot also cover daily customer support without another owner.
REQUIREMENT 34 / 100 · Founder
Decision authority Prevent conflicting instructions and stalled approvals.
Required actions Name the budget approver, product approver and final commercial signatory. Set spending limits and escalation rules. Record how disagreements and unavailable approvers are handled. Review standard
Working record Decision type and authority Limit / delegated authority Escalation and substitute Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The marketing owner may test within an approved cap but cannot change the supplier PO.
REQUIREMENT 35 / 100 · Founder
Existing resources and constraints Use assets that genuinely reduce launch difficulty.
Required actions Inventory the audience, distribution, expertise, suppliers and team already available. Attach evidence of access, capacity and commercial terms. Record restrictions such as geography, working hours, storage or seasonal demand. Review standard
Working record Resource and evidence Usable capacity / terms Constraint and effect on scope Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An audience’s follower count is separate from evidence that its members buy this category.
REQUIREMENT 36 / 100 · Founder
Category shortlist Compare two or three narrow opportunities on the same basis.
Required actions Score buyer evidence, founder fit, supply access, contribution and operating complexity. Record the evidence behind each score and what remains unknown. Review trade-offs before selecting one launch scope; do not use a growth ranking alone. Review standard
Working record Category and launch scope Evidence by decision criterion Trade-offs and recommendation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Skincare and home cleaning may both repeat, but release requirements, packaging and shipment costs differ.
Related requirements: 31, 32, 35, 41
REQUIREMENT 37 / 100 · Founder
Capital-to-scope fit Reduce the range when the funded plan is too large.
Required actions Build the full cost of the proposed SKU count, channel mix and launch geography. Include samples, minimum orders, overhead, reorder cash and a reserve. Remove optional variants or channels before compromising required product checks. Review standard
Working record Proposed scope and total cost Funded amount and reserve Scope removed or deferred Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note One product in two pack sizes may still create two packaging MOQs and separate stock exposure.
REQUIREMENT 38 / 100 · Founder
Business and supply route Choose the operating model deliberately.
Required actions Compare own manufacturing, contract manufacture, private label and distribution where relevant. Document control over specification, lead time, IP, margin and working capital. Obtain qualified advice on the obligations created by the actual product and route. Review standard
Working record Routes considered Commercial and operational comparison Chosen route and unresolved obligations Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Private label can shorten development but does not remove the need to review product and claim suitability.
REQUIREMENT 39 / 100 · Founder
Launch geography Define where the business can reliably sell and serve.
Required actions Select cities or pincodes, languages and shipping conditions. Check serviceability, charges, return handling and any product-specific transport limits. Align targeting, product pages and support promises to that scope. Review standard
Working record Geography and language Serviceability and restrictions Delivery and support promise Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A fragile home product can start in fewer lanes until transit damage and reverse logistics are understood.
REQUIREMENT 40 / 100 · Founder
Investment stop conditions Agree when the founder will pause further commitment.
Required actions Set evidence, cash, quality and delay conditions before major spending. Define the decision owner and what commitments can still be cancelled or deferred. Review the conditions at each release or reorder gate. Review standard
Working record Trigger and threshold Exposure / commitments affected Owner and corrective decision Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Pause a reorder if unresolved product complaints or forecast cash fall beyond the agreed limits.
Related requirements: 32, 37
Customer evidence Test purchase behaviour, the offer and the reason to switch.
REQUIREMENT 41 / 100 · Research owner
Buyer profile Describe a buying situation that can be researched and served.
Required actions Record the occasion, current product, purchase channel and actual spend. Identify suitability needs and what causes dissatisfaction. Use observed behaviour to define the first segment rather than broad demographics alone. Review standard
Working record Buying occasion and current alternative Actual spend and channel Problem and evidence Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note “People replacing an uncomfortable daily moisturiser” is more testable than “everyone aged 18–40.”
REQUIREMENT 42 / 100 · Research owner
Purchase-evidence interviews Learn from actual behaviour before asking for opinions on an idea.
Required actions Ask about the last purchase, alternatives considered, price and what happened after use. Record the respondent code, date, source and important contrary evidence. Separate reported facts from interpretation and avoid treating interview count as market demand. Review standard
Working record Respondent code and date Last purchase and use experience Evidence, interpretation and contrary finding Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A stated intention to buy becomes a hypothesis until an offer is tested at a real price.
REQUIREMENT 43 / 100 · Research owner
Competitor comparison Compare the products a customer would actually consider.
Required actions Capture the variant, pack quantity, displayed price, channel, date and source. Separate MRP, paid price, conditional offers and delivery charges. Compare claims as brand statements and avoid unsupported unit conversions. Review standard
Working record Product / variant and source Price, quantity, channel and date Comparison and limitation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A 50 g pack and a 50 ml pack cannot be assumed equivalent without a valid conversion.
REQUIREMENT 44 / 100 · Research owner
Review analysis Find recurring concerns without inventing prevalence.
Required actions Define the platforms, date range and review sample used. Code themes such as quality, fit, packaging, delivery and value; retain source references. Report the denominator, sampling bias and conflicting evidence before suggesting a product change. Review standard
Working record Sample and sources Themes with counts / denominator Limitations and product implication Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Eight leakage mentions among 60 selected reviews are a sample observation, not a category defect rate.
REQUIREMENT 45 / 100 · Research owner
Reason to switch Make the proposed advantage relevant and supportable.
Required actions Name the current alternative and the specific improvement the buyer values. Connect the proposed benefit to evidence from the actual product. Check whether the advantage survives the real price, delivery charge and inconvenience of switching. Review standard
Working record Current alternative Proposed improvement and proof Price / switching objection Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A better dispensing pack may matter only if users experience the current pack as wasteful.
REQUIREMENT 46 / 100 · Research owner
Initial market segment Keep the first launch narrow enough to learn from.
Required actions Select one use case, buyer group and geographic scope. Define who the initial offer is not designed for. Choose channels and support language appropriate to that segment. Review standard
Working record Initial segment and use case Excluded uses / buyers Channel and geography Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A workday lunch container for commuters is a narrower starting scope than all kitchen storage.
REQUIREMENT 47 / 100 · Research owner
Price validation Test willingness to pay at the intended commercial offer.
Required actions Show the real pack, quantity, delivery conditions and price. Record accepted purchases, refusals and the reason given. Compare results across a defined sample and retain the effect of discounts separately. Review standard
Working record Offer and total payable price Sample / purchases / refusals Objections and pricing decision Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A discounted trial does not establish full-price demand unless the discount effect is examined.
REQUIREMENT 48 / 100 · Research owner
Controlled paid pilot Learn from an offer the business can deliver responsibly.
Required actions Approve the product, quantity, customer terms, fulfilment and support process before accepting payment. Cap the pilot by stock, cash and service capacity. Record delivery, refunds, issues and customer feedback; arrange clear remedies for unmet promises. Review standard
Working record Pilot offer and deliverable stock Customer terms and spend cap Retained results, issues and remedies Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A 40-order pilot tests the actual pack and dispatch process before a broader campaign.
Related requirements: 47, 49, 56, 57, 76
REQUIREMENT 49 / 100 · Research owner
Predefined test criteria Prevent a weak result from being reinterpreted after the event.
Required actions State the question, sample, duration and maximum spend. Define success, stop conditions and what would make the result inconclusive. Assign an owner and review date before starting. Review standard
Working record Question, sample and duration Budget, pass and stop conditions Owner and review date Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A price test with too few eligible visitors may be inconclusive even when two purchases occur.
REQUIREMENT 50 / 100 · Research owner
Validation decision Turn research into an explicit investment decision.
Required actions Summarise supporting and opposing evidence against the pre-agreed test. Choose proceed, modify, retest or stop and record the reason. Define the next commitment, owner and evidence gate. Review standard
Working record Evidence summary Decision and rationale Next commitment and gate Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Proceed to supplier samples while deferring a full inventory order until product checks are complete.
Related requirements: 42, 47, 48, 49
Product and suppliers Control specifications, samples, purchase orders and release.
REQUIREMENT 51 / 100 · Product / sourcing owner
Hero product brief Give everyone the same definition of the initial product.
Required actions Describe the buyer, occasion, problem, product format and intended price. Record the expected performance, pack quantity, variants and exclusions. Link the brief to the current evidence and approved specification version. Review standard
Working record Buyer / problem / intended benefit Format, quantity, variants and price Evidence and brief version Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A daily cleanser brief names the intended user experience and pack, without unsupported treatment claims.
REQUIREMENT 52 / 100 · Product / sourcing owner
Assortment and variant limit Expose the cash and operational cost of adding another option.
Required actions List the role of every SKU and variant. Calculate incremental MOQ, packaging, testing, creative, stock and support complexity. Approve additions only when the expected benefit justifies the funded cost. Review standard
Working record SKU / variant and role Incremental cost and MOQ Evidence and approval decision Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A new fragrance can require separate packaging and stock even when the base formula is shared.
REQUIREMENT 53 / 100 · Product / sourcing owner
Product specification Make product quality measurable for the actual category.
Required actions Document ingredients or materials, dimensions or fill quantity, tolerances and performance requirements as relevant. Specify packaging, storage, transport and traceability needs. Have the appropriate technical reviewer approve the version used for samples and production. Review standard
Working record Technical specification and tolerances Packaging / storage / traceability Approved version and technical reviewer Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note For apparel, size tolerances and wash behaviour replace skincare-specific formulation fields.
REQUIREMENT 54 / 100 · Product / sourcing owner
Comparable quotation request Obtain offers that can be compared on the same scope.
Required actions Send the same product specification, quantity and packaging requirements to each supplier. Request itemised unit costs, tooling, tests, freight, taxes, MOQ, validity and lead time. Record exclusions, payment dates and the remedy for defects or substitutions. Review standard
Working record Specification and quantity issued Itemised quotation and validity Exclusions, payment and remedy terms Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A cheaper ex-factory price may become more expensive after packaging, freight and tooling.
Related requirements: 51, 53
REQUIREMENT 55 / 100 · Product / sourcing owner
Component-level minimum orders Find the smallest practical production commitment.
Required actions Record MOQ for finished product, bottle, closure, label, carton, colour and other relevant components. Identify excess or unused components and their ownership and storage cost. Align purchasing with usable product yield and future reorders. Review standard
Working record Component and MOQ Required, excess and usable quantity Cash cost, storage and ownership Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A 1,000-unit fill can still require 3,000 printed cartons; the extra cartons consume cash.
REQUIREMENT 56 / 100 · Product / sourcing owner
Sample evaluation Approve a reference sample through recorded criteria.
Required actions Define checks against the specification, use experience and packaging requirements. Record sample version, test conditions, defects and required revisions. Retain an approved reference and reviewer sign-off before production release. Review standard
Working record Sample ID and version Checks, results and defects Approved reference and reviewer Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A visual sample approval does not replace the applicable technical or safety assessment.
Related requirements: 53, 54
REQUIREMENT 57 / 100 · Product / sourcing owner
Product-specific release review Identify the qualified checks required for the actual product.
Required actions Ask the responsible specialist to determine classification, applicable licences, tests, labels and release records. Record the current source, scope, reviewer and evidence for each requirement. Keep sale and claims on hold where required approvals or evidence are missing. Review standard
Working record Product route and applicable requirement Reviewer, source and test / licence evidence Release decision and unresolved condition Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The same broad category can contain products with different obligations; this checklist is not an approval.
Related requirements: 53, 56, 58
REQUIREMENT 58 / 100 · Product / sourcing owner
Claims evidence register Control what appears on packaging, pages and advertising.
Required actions Record the exact proposed claim and every place it will appear. Link evidence to the actual product, method, population and conditions assessed. Have the appropriate reviewer approve wording, limitations and review dates. Review standard
Working record Exact claim and placement Evidence scope and limitations Approved wording, reviewer and date Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A supplier ingredient study does not automatically substantiate the finished product’s performance.
REQUIREMENT 59 / 100 · Product / sourcing owner
Purchase-order terms Make the production commitment specific and enforceable through the agreed contract.
Required actions Reference specification, approved sample, quantities, price and delivery schedule. Record deposits, balance triggers, inspection, defects and substitution controls. Agree ownership, cancellation and dispute terms with appropriate commercial or legal review. Review standard
Working record PO, specification, quantity and dates Payment / inspection / defect terms Ownership, substitution and contract review Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A message saying “same as sample” is insufficient if the sample version and acceptance criteria are unclear.
Related requirements: 54, 55, 56, 57
REQUIREMENT 60 / 100 · Product / sourcing owner
Supply contingency Plan for a supplier or component failure before launch.
Required actions Identify single-source components and realistic replacement lead times. Check backup compatibility, qualification requirements and minimum orders. Define reserve stock, recovery cost, customer communication and decision ownership. Review standard
Working record Failure scenario and exposure Qualified backup / validation needed Recovery time, cost and owner Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An alternative pump must be checked with the actual bottle and product before it is substituted.
Related requirements: 54, 55
Economics and cash Connect retained sales, contribution, working capital and risk.
REQUIREMENT 61 / 100 · Finance owner
Landed product cost Build the cost from usable units rather than the quoted factory price.
Required actions Include product, primary and secondary pack, inbound freight, handling and applicable non-recoverable charges. Allocate tooling and tests on an explicit basis; separate recoverable tax and one-time spending. Use expected usable yield and record source quotations and dates. Review standard
Working record Cost components and sources Tax / allocation basis Usable units and landed cost Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A ₹200 factory unit may cost more after its bottle, carton, inbound freight and rejected units.
Related requirements: 54, 55
REQUIREMENT 62 / 100 · Finance owner
Gross-to-net revenue Use retained revenue rather than gross orders to judge performance.
Required actions Reconcile gross merchandise value, discounts, cancellations and refunds using mutually exclusive amounts. Remove applicable tax from retained collections using the correct rate or invoice-level treatment. Exclude shipping revenue from merchandise values or model it separately and reconcile to orders. Review standard
Working record Period and order scope Gross, discount, cancellation and refund bridge Tax basis and retained revenue reconciliation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The additional calculator uses one stated tax rate; mixed-rate baskets need line-level calculations.
REQUIREMENT 63 / 100 · Finance owner
SKU and bundle composition Know exactly what each sold offer consumes.
Required actions Link each offer to its component SKUs and quantities. Include inserts, gifts and outbound packing where relevant without duplicating costs. Check that prices and discounts support the full bundle cost and stock availability. Review standard
Working record Offer and component quantities Component costs and extra materials Net offer revenue and stock dependency Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A two-item routine bundle consumes one cleanser and one moisturiser even if shown as one order.
REQUIREMENT 64 / 100 · Finance owner
Contribution and operating balance Separate product margin, acquisition contribution and recurring costs.
Required actions Calculate net retained revenue less product, packing, fulfilment, losses and channel charges. Deduct acquisition and other variable selling costs on the stated customer basis. Deduct recurring costs separately and reconcile one-offs, finance and tax outside that balance. Review standard
Working record Revenue and variable cost basis Acquisition and contribution Recurring costs and excluded items Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Positive product margin can coexist with negative contribution after customer acquisition.
Related requirements: 61, 62, 63
REQUIREMENT 65 / 100 · Finance owner
Channel profitability Assess each route using its own cost and settlement terms.
Required actions Capture commissions, payment, fulfilment, promotions, return charges and deductions. Allocate costs consistently and avoid counting brand and platform-funded offers twice. Reconcile settlements to orders and add settlement delays to the cash forecast. Review standard
Working record Channel fee and deduction schedule Retained orders and contribution Settlement timing and reconciliation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Marketplace GMV and website net sales need a common retained-sales definition before comparison.
REQUIREMENT 66 / 100 · Finance owner
Allowable acquisition cost Set an acquisition ceiling supported by contribution.
Required actions Start with pre-acquisition contribution on a retained first order. Deduct the contribution required for overhead and the chosen risk buffer. Extend payback only with observed mature repeat contribution and a funded cash horizon. Review standard
Working record First-order contribution Required reserve and CAC ceiling Payback evidence and cash limit Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note With ₹600 pre-acquisition contribution and ₹200 reserve, an illustrative CAC ceiling is ₹400.
Related requirements: 64, 65
REQUIREMENT 67 / 100 · Finance owner
Break-even and capacity Check whether break-even volume is operationally attainable.
Required actions Divide recurring cost by contribution after the planned acquisition mix. Round required retained orders up and compare with stock, fulfilment and support capacity. Show no finite break-even when contribution is zero or negative. Review standard
Working record Recurring cost and contribution basis Required retained orders Capacity and constraint Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note ₹2 lakh recurring cost at ₹250 contribution requires 800 retained orders before excluded items.
Related requirements: 64, 66
REQUIREMENT 68 / 100 · Finance owner
Dated launch budget Translate a capital allocation into payment commitments.
Required actions Allocate research, product, inventory, store, creative, launch spend, people and reserve. Separate estimate, quote, commitment and paid amount. Assign due dates and approval limits, then feed the schedule into the cash forecast. Review standard
Working record Budget item and evidence level Allocated, committed and paid Due date and approval Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An inventory deposit and final balance are separate dates even when one PO covers both.
REQUIREMENT 69 / 100 · Finance owner
13-week cash forecast Expose the week cash becomes constrained.
Required actions Enter opening cash and actual expected collections rather than booked sales. Schedule supplier payments, media, people, refunds, tax and other cash outflows. Review closing cash and the minimum reserve every week; reconcile forecasts with actuals. Review standard
Working record Opening cash and collection basis Dated inflows and outflows Reserve, low point and corrective action Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A profitable month can still have a cash shortfall before marketplace settlements arrive.
Related requirements: 32, 68
REQUIREMENT 70 / 100 · Finance owner
Downside cash cases Test the impact of delay or weaker trading before scaling.
Required actions Model delayed collections, higher acquisition spend, excess stock and changed supplier payments. Keep recoverable timing shifts separate from permanent revenue loss or added cost. Compare the lowest cash balance with the reserve and record a specific response. Review standard
Working record Scenario and changed assumptions Cash low point and reserve gap Action, owner and trigger Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The sensitivity tool shifts receipts by whole weeks and leaves receipts after week 13 outside the horizon.
Related requirements: 69
Brand and purchase experience Give customers the information and service needed to buy.
REQUIREMENT 71 / 100 · Brand / commerce owner
Name, domain and mark review Reduce identity conflicts before investing in packaging.
Required actions Shortlist names and check practical domain and social handle availability. Arrange an appropriate trademark or name review for intended markets and product classes. Record the reviewer, scope, date and decision before committing to production artwork. Review standard
Working record Names and practical availability Qualified review and scope Decision and commitment gate Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An available domain does not establish trademark clearance.
REQUIREMENT 72 / 100 · Brand / commerce owner
Brand standards Give every producer a usable visual and verbal reference.
Required actions Define fonts, colour values, spacing, logo use, photography and packaging rules. Set the tone, product terminology and claim boundaries. Store approved source files and examples with a version owner. Review standard
Working record Visual rules and source files Tone, terminology and claims Approved version and owner Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note The atlas uses ivory, charcoal and muted bronze; the founder’s product brand needs its own approved standards.
REQUIREMENT 73 / 100 · Brand / commerce owner
Complete product page Answer the questions that affect suitability and purchase.
Required actions Specify contents, quantity, materials or ingredients, use and important limitations. Show accurate images, price, availability, delivery and returns information. Check mobile presentation and route technical claims through the approved evidence register. Review standard
Working record Required product information Images, use and limitations Commercial information and QA result Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A bundle page lists every included item and quantity rather than showing only a lifestyle photograph.
Related requirements: 51, 57, 58, 75, 76
REQUIREMENT 74 / 100 · Brand / commerce owner
Actual product demonstration Make evidence visible in the buying journey.
Required actions Film or photograph the actual approved product and pack. Show the relevant use, scale, texture, fit, assembly or performance without misleading edits. Record consent, rights and conditions; use only supportable outcomes. Review standard
Working record Demonstration and product version Conditions and claim evidence Rights and approved placements Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A bag demonstration can show dimensions and compartments; an untested load claim should not be added.
REQUIREMENT 75 / 100 · Brand / commerce owner
Delivery information Set a promise the fulfilment operation can meet.
Required actions Confirm pincode serviceability, charges, dispatch cut-offs and delivery estimates. Identify product or location restrictions and peak-period exceptions. Keep product pages, checkout and support messages consistent. Review standard
Working record Pincode / route and charges Dispatch and delivery basis Restrictions and consistency check Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A dispatch estimate is distinct from the carrier’s expected transit time.
REQUIREMENT 76 / 100 · Brand / commerce owner
Returns and refunds information Make customer remedies understandable before purchase.
Required actions Define eligibility, time window, product conditions, exclusions and who pays relevant charges. Specify the request, inspection, approval and refund process. Have the policy reviewed for the actual product and selling route, then test its customer-facing presentation. Review standard
Working record Eligibility and conditions Request, approval and refund process Reviewed policy and display locations Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Personal care, apparel and fragile home products may need different handling; no universal policy is assumed.
REQUIREMENT 77 / 100 · Brand / commerce owner
Checkout and payment tests Find transaction failures before traffic is scaled.
Required actions Test success, failure, retry, duplicate submission and cancellation using the provider’s supported test process. Check order creation, inventory, customer messages and payment reconciliation. Test refund and recovery paths, record device and method, and close critical defects. Review standard
Working record Test case, device and payment method Expected and actual outcome Defect, owner and retest evidence Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A payment success screen is insufficient if the order was not created or stock was not deducted.
Related requirements: 73, 75, 76
REQUIREMENT 78 / 100 · Brand / commerce owner
Communication permissions Use contact data for the purpose the customer agreed to.
Required actions Separate transactional service messages from optional promotional communication. Record permission source, purpose, timestamp and withdrawal route where required. Review data access, retention and provider requirements with the responsible specialist. Review standard
Working record Purpose and permission basis Capture / withdrawal process Access, retention and reviewer Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An order-status message and a new-offer campaign need separately considered rules and customer controls.
REQUIREMENT 79 / 100 · Brand / commerce owner
Measurement definitions Make marketing and finance reports reconcile.
Required actions Define product view, checkout, paid order, delivered order, cancellation and retained order. Implement deduplication, test events and consistent attribution windows. Reconcile analytics to commerce and payment records; document consent and tracking limitations. Review standard
Working record Event and business definition Implementation / deduplication check Reconciliation and known limitation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A platform-reported purchase is not automatically a retained first-time customer.
REQUIREMENT 80 / 100 · Brand / commerce owner
Mobile and accessibility review Make the buying flow usable on the devices customers use.
Required actions Check readable text, contrast, tap targets, labels, keyboard focus and meaningful errors. Test slow loading, small screens and the complete purchase route. Record defects by impact and verify fixes before launch. Review standard
Working record Device / viewport and task Accessibility and performance findings Fix owner and retest Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A mobile comparison table may scroll within its container while the page remains within the screen.
Sales and repeat purchases Fund channel experiments and measure retained contribution.
REQUIREMENT 81 / 100 · Growth owner
First 100 customers Build a funded route to early retained purchases.
Required actions Allocate target customers across specific sources and offers. Record audience access, conversion assumptions, budget and an owner. Track actual retained customers and spend; deduplicate people across routes. Review standard
Working record Route, audience and offer Target, budget and owner Actual retained customers and learning Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Founder network 25, focused paid pilot 50 and partner route 25 are a plan, not achieved sales.
Related requirements: 46, 47, 48, 64
REQUIREMENT 82 / 100 · Growth owner
Channel experiments Give each channel a finite commercial test.
Required actions Define the audience, offer, destination, budget and measurement window. Set owner, stop rule and review date before spending. Assess retained customer cost, contribution and service effects before extending. Review standard
Working record Channel hypothesis and setup Budget, owner and review date Retained results and decision Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Search and discovery campaigns answer different questions and should not share an unexplained blended CAC.
Related requirements: 66, 73, 77, 79
REQUIREMENT 83 / 100 · Growth owner
Creative experiment register Learn which message works and why.
Required actions Record audience, occasion, opening message, proof, offer and destination. Change a limited number of variables and retain the version that ran. Review spend, retained orders, contribution and customer misunderstandings. Review standard
Working record Creative version and hypothesis Audience, proof and destination Spend, retained result and learning Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A texture demonstration and a price-led message may attract different buyers and complaint patterns.
REQUIREMENT 84 / 100 · Growth owner
Creator agreements Define content rights and commercial responsibilities before production.
Required actions Agree deliverables, revisions, fees, deadlines and approval process. Specify usage rights, territories, duration, paid-media permissions and disclosure requirements. Review product claims and retain the agreement and approved final asset. Review standard
Working record Deliverables, fees and schedule Usage rights and permissions Disclosure, claims and approved asset Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Receiving a video does not automatically grant unlimited paid advertising rights.
Related requirements: 58, 74
REQUIREMENT 85 / 100 · Growth owner
Search and product feeds Match high-intent queries with accurate product information.
Required actions Map category, problem, product and brand queries to suitable pages. Keep feed titles, identifiers, images, price, stock and destination consistent. Separate brand and non-brand performance and resolve feed errors before scaling. Review standard
Working record Intent and landing page Feed fields and error checks Brand / non-brand results Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A brand-name search may reflect demand created elsewhere rather than incremental discovery.
REQUIREMENT 86 / 100 · Growth owner
Marketplace readiness Check the full trading route before listing inventory.
Required actions Prepare listing content, identifiers, category documentation and stock integration. Review fees, promotions, returns, penalties and settlement terms for the actual account. Rehearse order, return and settlement reconciliation with named owners. Review standard
Working record Listing and document checklist Fees, returns and settlement terms Operational test and owner Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Platform fees vary by programme and terms; use the current account schedule rather than a generic rate.
REQUIREMENT 87 / 100 · Growth owner
Scale, hold or stop Increase spending only when evidence and capacity support it.
Required actions Set thresholds for retained CAC, contribution, complaints, stock and cash. Review a sufficiently mature period and note sample size and attribution limits. Approve the next budget and stock commitment together, with a rollback condition. Review standard
Working record Thresholds and review window Evidence and capacity Decision, budget and rollback trigger Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A winning acquisition test is held if the next production batch cannot arrive within the funded stock plan.
Related requirements: 69, 82, 83, 91, 93
REQUIREMENT 88 / 100 · Growth owner
Mature repeat cohorts Measure repeat only when customers had time to reorder.
Required actions Group buyers by first delivered purchase and relevant product-use cycle. Define eligibility, observation window and unique repeat buyers. Report immature cohorts separately and distinguish repeat customers from repeat orders. Review standard
Working record Cohort and eligibility rule Eligible buyers and repeat buyers Observation date and limitation Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A 45-day replenishment product cannot be assessed from customers who first received it last week.
Related requirements: 79
REQUIREMENT 89 / 100 · Growth owner
Lifecycle communication Support product use before asking for another purchase.
Required actions Map order, delivery, usage guidance, service and replenishment messages. Use relevant timing, permissions and suppression for complaints, returns or recent orders. Assign the owner, content version and measure useful outcomes rather than sends alone. Review standard
Working record Trigger, segment and message Permission and suppression rules Owner and outcome Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note An unresolved quality complaint suppresses a routine repurchase promotion until the issue is addressed.
REQUIREMENT 90 / 100 · Growth owner
Repeat-purchase contribution Check whether retention produces economic value.
Required actions Use net repeat revenue after discounts and refunds. Deduct product, fulfilment, payment, CRM, incentive and incremental service costs. Separate observed contribution from projected lifetime value and avoid double-counting campaign costs. Review standard
Working record Observed repeat orders and revenue Variable, CRM and service costs Contribution and period / cohort Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A higher repeat rate can still reduce value if discounts and contact costs exceed contribution.
Related requirements: 64, 88, 89
Delivery and governance Control stock, service, approvals, changes and handover.
REQUIREMENT 91 / 100 · Operations owner
Inventory and reorders Plan from usable stock and funded demand.
Required actions Reconcile usable, quarantined, committed and confirmed inbound stock by SKU or component. Apply demand, lead time, review period, safety stock and MOQ with explicit assumptions. Check expiry where relevant, cash and supplier capacity before authorising the reorder. Review standard
Working record Stock position and date Demand, lead time and MOQ Reorder quantity, cost and approval Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A bundle is constrained by its least-available component, even when finished-offer stock appears sufficient.
REQUIREMENT 92 / 100 · Operations owner
Fulfilment quality Control what happens between an order and a successful delivery.
Required actions Check item, quantity, address, pack, batch or serial reference as relevant. Record picking, packing, handover, tracking and exception ownership. Sample order accuracy and transit outcomes, then correct the cause of defects. Review standard
Working record Order / batch and checks Dispatch and tracking evidence Exception and corrective action Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Leakage, wrong variants and missing bundle components need separate causes and corrective actions.
REQUIREMENT 93 / 100 · Operations owner
Customer support and escalation Give customers a consistent route to resolution.
Required actions Define workflows for damage, quality, missing items, delays, refunds and suitability questions. Assign response and resolution owners and identify issues needing technical review. Keep relevant evidence, promised updates and closure confirmation without unnecessary personal data. Review standard
Working record Issue type and evidence Owner, promised update and remedy Escalation and closure Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A quality complaint may require batch investigation rather than only a replacement shipment.
REQUIREMENT 94 / 100 · Operations owner
Dependency-based launch calendar Make dates depend on the work required to release and deliver.
Required actions Link research, samples, product review, packaging, production, store and fulfilment gates. Name owners and actual lead times, including approval time. Move dependent work and revise cash when a prerequisite slips. Review standard
Working record Milestone, owner and predecessor Planned / actual date Delay effect and revised cash action Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Paid acquisition cannot assume launch while the approved pack or product release is still pending.
Related requirements: 50, 56, 57, 59, 77
REQUIREMENT 95 / 100 · Operations owner
Weekly operating review Use one review to connect commercial and operational decisions.
Required actions Compare planned and actual retained orders, sales, contribution, cash and stock. Review customer issues, test outcomes and upcoming commitments. Record decisions, owners, due dates and what changed in the forecast. Review standard
Working record Week and plan versus actual Causes, stock, cash and customer issues Decisions, owners and due dates Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A sales shortfall caused by stock unavailability needs a different response from an offer-conversion problem.
REQUIREMENT 96 / 100 · Operations owner
Scope changes Prevent new requests from silently changing fees and dates.
Required actions Describe the requested change and why it is needed. Assess effects on outputs, revisions, cost, dependencies and timeline. Obtain the authorised decision before starting and retain the baseline and new version. Review standard
Working record Change and reason Cost, scope and schedule impact Approver, decision and effective version Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note Adding another product variant is assessed for sourcing, testing, artwork and inventory effects.
REQUIREMENT 97 / 100 · Operations owner
Shared client portal Specify authenticated collaboration separately from local planning.
Required actions Define project membership and role-based access for founder, team, specialist and viewer. Require server-side authorisation, project isolation, version history, protected files and attributable approvals. Test invitation, revocation, recovery, backup and audit retention before enabling real client collaboration. Review standard
Working record Roles and access matrix Security / collaboration acceptance tests Hosting, identity, deployment and reviewer Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note This edition saves on one browser. Shared accounts, cloud sync and authenticated approvals are not enabled.
REQUIREMENT 98 / 100 · Operations owner
Milestone acceptance Connect delivery evidence to the agreed commercial gate.
Required actions List the exact deliverable version and acceptance criteria. Record the authorised reviewer, requested changes and acceptance evidence. Track invoice or payment status separately; do not treat a local checkbox as a signature. Review standard
Working record Milestone and deliverable version Acceptance evidence / required changes Authorised approver and payment status Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A weekly report may be delivered while the product-release milestone remains unaccepted.
Related requirements: 26, 27, 34
REQUIREMENT 99 / 100 · Operations owner
Issue and decision history Retain the reasoning behind changes to the business.
Required actions Record the issue, date, financial or customer exposure and evidence. Name the decision owner, options, deadline and chosen response. Close only after checking the result; retain reopened issues and superseded decisions. Review standard
Working record Issue and exposure Options, decision, owner and due date Resolution evidence and follow-up Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A supplier delay decision records the extra cash requirement and the customer promise affected.
REQUIREMENT 100 / 100 · Operations owner
Handover and exit Leave the founder able to operate the business after the engagement.
Required actions Transfer the agreed accounts, source files, supplier records, SOPs and approved work. Verify access and recovery with the receiving owner; revoke access that is no longer required. List open issues, licences, renewals, commitments and the next operating plan. Review standard
Working record Asset / SOP and receiving owner Transfer, access and recovery check Open issues, commitments and next plan Add a record title, reference, version and date. Assign an owner and due date. Retain review evidence, reviewer, status and open issues.
Practical example / note A folder link is incomplete handover if the brand cannot edit source files or recover its domain.
Related requirements: 30, 96, 98, 99
Prepared for Rishi · @brandlyhumann
The guide provides a framework for recorded work. It does not represent completed research, verified suppliers, legal approvals, client results or guaranteed sales.