THE SEEKER FOUNDATION × SANATAACLIENT SCOPE

Build the system.Then the footprint.

A client-facing scope and strategic expansion blueprint: grounded first in the decisions made with Sanataa, strengthened by TSF’s operating model, and supported—only where useful—by Leonid’s distribution lens.

POSITIONINGSanataa Marathi Kitchen
TSF’S ROLEBusiness Management & Expansion Office
THE AIMA model that earns the right to replicate
Prepared under the direction of Dhiraj · Engagement Director, TSFConfidential · 30 August 2026
READ THIS FIRSTSource hierarchy

Client truth leads.
Strategy follows.

This version corrects the earlier emphasis. The 25 August scope-alignment record is the governing spine. TSF’s concept work explains how the agreed direction can operate. Leonid appears in only two mid-deck sections, as a specialist distribution contribution—not as the engagement itself.

01 · Governing

Meeting record

Decisions, roles, expectations, client concerns, constraints and the verbally communicated scope. This controls what TSF is proposing.

First in authority
02 · Product authority

26 August menu

The base product universe for culinary decomposition, recipe work, CK planning, service design and commercial validation.

Governs product
03 · TSF modelling

Concept design

The operating thesis, format, distribution architecture, decision gates and replication logic. These remain working recommendations until validated.

Explains the answer
04 · Specialist input

Leonid strategy

Independent verbal-brief thinking on demand, content and distribution. Introduced formally after sign-up under a separate specialist proposal.

Supports two sections
Where sources disagree, this deck shows the decision—not a convenient synthesis.Capital, property, launch-channel and product claims stay open until the evidence needed to close them exists.
02
THE MEETING IN ONE PAGE

One brand.
One decision line.

The alignment meeting did more than discuss an outlet. It decided how Sanataa will think, approve and sequence a multi-asset transformation.

Business & brand sponsor

Isha

Leads execution across the domain and carries the single line of communication for brand, marketing and expansion decisions.

Protects speed and coherence
Founder & product custodian

Varsha ji

Guards recipe truth, taste, quality and finance decisions—guided by the best business outcome without compromising product integrity.

Protects the foundation
Expansion office

TSF · Dhiraj

Recommends, connects, records, challenges and keeps specialists working to one approved brief. TSF does not take the client’s decision rights.

Protects the programme
01Recommend
options + implications02Decide
one named authority03Record
decision + due date04Execute
one authorised instruction
Implementation rationale · why the single decision line matters

Mental bandwidth is capital.

When founders repeatedly reopen a settled choice, the cost appears later as delayed vendors, changed drawings, unclear hiring and missed launch dependencies. TSF will maintain a decision register and make timeline impact visible when a reserved decision remains open.

Deadlock becomes a process.

TSF recommends options; Sanataa decides. If the named owner does not close a decision by its due date, dependent work pauses. This is not rigidity—it is how quality and capital are protected from informal drift.

THE ENGAGEMENT TRUTHMeeting record

TSF is the expansion office.
Not the contractor.

TSF IS

The advisory brain and coordination layer

  • One operating brief across concept, culinary, people, infrastructure, brand and launch.
  • An objective eye on necessity, quality, timing and approval readiness.
  • A programme governor that connects dependencies and keeps decisions visible.
  • A specialist briefer and reviewer—culinary, layout, architecture, brand, compliance and technology.
  • A capability builder: roles, scorecards, systems, trials, reporting and replication gates.
TSF IS NOT

A shadow operator or vendor database

  • Not the contractor, purchaser, statutory applicant or holder of client funds.
  • Not a substitute for Sanataa’s Storekeeper, accountant, managers or operating team.
  • Not committed to pushing TSF contacts when the market offers a better answer.
  • Not responsible for local trades that should be sourced and managed locally.
  • Not a guarantor of approvals, sales, profit or timelines that depend on client decisions and external parties.
TSF guides and governs. Sanataa decides, contracts, pays, employs and operates.
04
WHAT THE CLIENT ASKED THIS MODEL TO HOLD

Accessible product.
Serious ambition.

The opportunity sits inside a deliberate tension: strong value and stomach-full portions, expressed through a more coherent flagship, without building an expensive “premium restaurant” that the menu cannot support.

CLIENT AMBITION₹1L

gross sales per day

An ambition—not a forecast. It needs a multi-channel transaction model, disciplined menu contribution, enough throughput and a repeat engine. Marketing is expected to convert to revenue, not merely look active.

PRODUCT ECONOMY

~33% food cost is a working figure

It remains unverified until recipe costing, yields, wastage, stock counts and channel economics are operating.

GROWTH PACE

Slow enough to sustain

Hold six months of outlet operating runway. Do not allow visibility or announced timelines to outrun operating readiness.

EXPERIENCE

Better—not overbuilt

Seating, comfort, cleanliness and service matter. Super-premium décor is not the proposition.

Closed in the meeting

  • Borivali first; let market evidence guide the exact address.
  • New flagship precedes the full Dahisar revamp.
  • Target generations together; agency to refine personas.
  • Real success is sustenance—not a paid award.

Still requires evidence

  • Capital envelope and phase allocation.
  • CK equipment, people and compliance path.
  • Six-month marketing investment.
  • Exact property, format and launch-channel decision.
Implementation rationale · the contradictions TSF must manage openly

Premium versus volume

The product price, household relevance and fast-casual service point toward “premium-accessible,” not “premium restaurant.” The first format must increase trust and perceived order without forcing guests to pay for design theatre.

Ambition versus evidence

₹1 lakh/day can only become a plan after transaction capacity, average bill value, channel commission, food cost, labour, occupancy and repeat are modelled from actual inputs. TSF will build the bridge—not treat the headline as a promise.

05
CAPITAL FOLLOWS READINESS

Three assets.
One sequence.

The transformation should be built as a chain of capabilities. Each asset earns permission for the next; none should be treated as an isolated construction project.

ASSET 01CK

Central Kitchen

Standardise semi-finished production, quality, batch control, packaging, dispatch and take-home lines.

FIRST PURPOSE · REPEATABLE PRODUCT
ASSET 0202

Borivali Flagship

Prove the new customer experience, service flow, product mix, distribution model and team ownership.

FIRST PURPOSE · REPEATABLE FORMAT
ASSET 0301

Dahisar Revamp

Move kitchen load to CK, expand seating, modernise the legacy outlet and apply what Outlet 2 has proven.

GATE · OUTLET 2 REVENUE + CK STABILITY
G1

One brief

Can founders and teams approve one concept, one menu base and one decision architecture?

G2

Legal + technical

Can the chosen site support food safety, utilities, exhaust, drainage, fire and operating flow?

G3

Team reproducibility

Can documented recipes and trained people reproduce the promise without founder heroics?

G4

Business sustenance

Can the unit hold quality, contribution and repeat before capital is committed to replication?

Backend integration · what “CK first” actually means

Not a large kitchen for its own sake.

The CK’s first job is to remove variance and founder dependence from bases, prep, batches, packing and dispatch. Its required equipment comes after culinary decomposition of the 26 August menu—not before.

December remains a target, not a waiver.

The meeting accepted December 2026 as more realistic for saleable CK output. Licences, gas, drainage, exhaust, fire/society permissions, team and trials are still release conditions. If the outlet property is delayed, CK may support a festive activation only if readiness passes.

THE REPOSITIONINGTSF model

A Marathi Kitchen.
Built for frequency.

PUBLIC POSITIONING LOCK

Sanataa Marathi Kitchen

A clean, contemporary and value-accessible vegetarian Maharashtrian fast-casual brand for everyday meals, all-day snacks, upvas occasions and take-home purchase.

THE OPERATING ENGINE

Organised poli-bhaji utility

Familiar food, predictable availability, fast service, hygiene and value. This is how the business earns frequency; it is not the public label.

THE VALIDATED VERTICALS

Mithai, farsan, retail and gifting

These increase household relevance and average bill value, but should enter only through make/buy, quality, shelf-life and supply-chain validation.

THE CLEAR NO

Not a generic café or premium Maharashtrian restaurant

Modern expression cannot dilute regional authority, value, speed or the customer’s reason to return often.

Sanataa today

  • Founder-dependent taste
  • Mixed menu perception
  • One neighbourhood shop
  • Food-only transactions
→

Sanataa being built

  • Recorded product standards
  • Clear Marathi authority
  • CK-fed neighbourhood system
  • Meal + beverage + take-home basket
Decision rationale · why “Mithai” is not locked into the name yet

Positioning must match controllable capability.

Sanataa currently has limited in-house sweets capability. Placing Mithai inside the headline promise before the make/buy model, sensory standard, supply consistency and calendar range are validated can create a claim the opening team cannot defend.

The commercial role remains important.

Sweets and farsan can still sit visibly within the store, calendar and gifting architecture. The naming choice should be revisited only after Culinary and the client prove that the vertical can behave like a brand promise—not a sourced assortment.

07
THE FIRST CUSTOMER MACHINE

Fast at the counter.
Warm at the table.

The first Borivali format is a 650–850 sq ft working band—not a drawing claim. The exact area allocation will be validated through a dimensionally accurate model after site and equipment inputs exist.

The intended service journey

01

Choose + pay

One primary food-order counter. The menu is organised by occasion and speed.

02

Token maps table

A physical table token links the bill to the guest without another queue.

03

Runner serves

Food runners protect hospitality while keeping service fast and clear.

04

Beverage separates

Tea, coffee, panha and chaas move in their own production and pick-up rhythm.

05

Exit distributes

Take-home, preorder and owned-audience opt-in extend the relationship beyond the table.

FOOTPRINT

650–850 sq ft

Proposition band only. Seating, BOH, retail, rider hand-off and beverage allocation require measured validation.

FORMAT STUDY

AC versus open

Test comfort, monsoon, dust, noise, food safety, energy and dwell. No format choice is final before evidence.

SEATING

Right-sized after flow

No fixed seat claim until the plan proves access, aisle, queue, runner and evacuation clearances.

CHANNELS

One production truth

Dine-in, takeaway, pickup and delivery cannot be four uncoordinated queues fighting one pass.

Open point · dimensional visual is validation, not decoration

Inputs needed first

Measured shell, frontage, columns, services, equipment schedule, menu throughput, rider requirement, storage days, staffing and legal clearances.

What the visual must prove

Guest queue, table count, runner travel, beverage flow, food pass, takeaway hand-off, dirty return, retail visibility, staff movement and peak-hour collision points. Until then, 650–850 sq ft remains a disciplined hypothesis.

THE BORIVALI LENSDirectional · no rents

Choose the household.
Then the address.

The shortlist below is a demographic and occasion hypothesis. It does not rank available properties and intentionally excludes rent. Post-sign-up fieldwork must test frontage, walking patterns, competition, delivery access, daypart demand and household behaviour.

RankLocalityLikely demand characterBest strategic roleValidate
01

Shimpoli

Best balance

Dense families, students and routine-led local movement.

Everyday kitchen + subscription acquisition.

Frontage, evening conversion, rider access.

02

Chikoowadi

Household fit

Family-led residential demand; stronger quality, health and convenience cues.

Meals, bhakri plans, take-home and gifting.

Owned demand versus lower impulse footfall.

03

Chandavarkar Rd

Visibility test

Mixed-age food discovery and destination behaviour.

Brand theatre, discovery and content capture.

Competitive clarity within five seconds.

04

Babhai Naka

Category familiarity

Mature residential-commercial mix and family eating occasions.

Classics, upvas, snacks and take-home.

Sanataa conversion versus generic category purchase.

05

Vajira Naka

Everyday relevance

Dense, value-aware families with frequent local food occasions.

Routine meals, bundles and fixed-slot delivery.

Accessible expression; not premium-remote.

06

LT Road

High comparison

Transit, shopping and existing sweets-farsan habit.

Acquisition, gifting and digital visibility.

Lead with Kitchen; do not read as another sweet shop.

07

SV Road

Visibility-led

Commuters, vehicles and a wider delivery catchment.

Takeaway, aggregator throughput and recall.

Pedestrian conversion, access, parking, rider staging.

Field method · how TSF will turn the shortlist into a recommendation

Demand evidence

Daypart walks, household intercepts, competitor observation, bill-value checks, delivery-radius mapping, school/office/community anchors and category search behaviour.

Format evidence

Frontage, visible queue capacity, rider access, service entries, utilities, exhaust route, drainage, storage, legal use, operating restrictions and measured shell. The address is chosen after the format and the demand both pass.

LEONID INPUT · SECTION 1 OF 2
09
THE OUTSIDE-IN DIAGNOSIS

Loved by a lane.
Under-distributed by a belt.

Leonid’s independent verbal-brief work validates an important TSF conclusion: Sanataa’s next constraint is not simply product creation. It is consistent reputation, repeated discovery and a reason for the neighbourhood to choose again.

Footfall leader.Reputation follower.

The public signals in Leonid’s August 2026 scan show long-lived local proof but a weak digital reputation and content system relative to the competitive belt. The strategic task is to convert offline affection into visible, searchable and repeatable demand.

24YEARS OF LOCAL EQUITY

A legacy advantage that cannot be manufactured by a new entrant.

805GOOGLE REVIEWS

Meaningful proof, but rating and velocity need active management.

3.7PUBLIC RATING SNAPSHOT

Below Leonid’s cited belt benchmark; verify live before use externally.

102INSTAGRAM FOLLOWERS

A symptom of under-distribution, not a vanity target by itself.

The edge is trust + rooted Marathi food + frequency. The weakness is that this edge has not yet become a system people can discover, remember and carry into their homes. The sequence is local proof first, a Mumbai cluster second, and outstation commerce only when the name can travel.
Integration boundary · what TSF takes from Leonid here

Accepted strategic contribution

Deepen the home market before widening; treat Maps, reviews, content, search and owned audience as distribution infrastructure; measure conversion and repeat rather than post volume.

Not a replacement for the client scope

Leonid’s full proposal remains separate and is introduced after sign-up. TSF retains responsibility for the combined business brief, commercial gates and integration with Culinary and operations.

LEONID INPUT · SECTION 2 OF 2
10
THE DISTRIBUTION ENGINE

Stop being a menu.
Become a calendar.

Calendar builds family ritual and predictable purchase. Drops create novelty and talkability for younger audiences. Every approved activation becomes product, content, preorder, WhatsApp growth and post-event learning.

01Occasion truth02Culinary-approved product03Real Marathi-first story04Local discovery05Visit / preorder / opt-in06Repeat + learning

Working Panchang and opportunity map only. Mumbai tithi, moonrise, dietary interpretation, production capacity and products must be revalidated annually and 60 days before every activation. Every product shown is a Culinary brief—not an approved menu promise.

HOUSEHOLD UTILITY

Everyday essentials

Jowar bhakri, spiced bhakri and selected ghavan / meal components in a limited hyperlocal radius. Prepaid or wallet-based, with fixed production and delivery windows—not on-demand promises.

RITUAL UTILITY

Upvas calendar pass

Ekadashi and Sankashti reminders, preorder cut-offs and curated meal access through WhatsApp. This removes planning effort for the household while making CK demand more visible.

OCCASION UTILITY

Festival circle

Early access, deposits and capacity-capped drops for modak, faral, puranpoli, tilgul and seasonal boxes. The value is assured fulfilment—not indiscriminate discounting.

Operating design · how Calendar × Drops functions

Calendar

Ekadashi, Sankashti, Ganeshotsav, Diwali, Sankranti, Holi, Gudi Padwa, Ashadhi and recurring Sunday rituals become planned demand windows. Preorder cut-offs and capacity make demand visible before production.

Drops

Limited archival recipes, regional grains, festival specials and story-rich products test demand without permanent menu complexity. Culinary validates feasibility; Leonid builds expression; TSF sets the commercial and operating gate.

Content is proof

Hands, batches, recipes, origins, morning prep, real customers and calendar meaning. The content must make the food easier to trust and buy—not turn Sanataa into an entertainment company.

Six measures

Search visibility, review velocity, local reach, visit/order conversion, WhatsApp opt-in and repeat. Every activation needs an objective, owner, capacity, code and post-mortem.

Subscription infrastructure

CK slot planning, labelled packs, route batches, insulated dispatch, prepaid ledger or wallet, WhatsApp CRM, pause/skip rules, customer-service owner, cut-offs and exception handling. Pilot one pin-code cluster before widening.

Working trade-off

Subscriptions can build habit, forecast demand and reduce acquisition cost. They can also create last-mile cost, exceptions and fulfilment pressure. The pilot must prove contribution, retention and delivery density—not only subscriber count.

OWN THE STANDARD · NOT EVERY MACHINEFor Culinary + client validation

Make selectively.
Specify everything.

The opening model should not depend on a heavy, specialist sweets or farsan kitchen. Sanataa can still own quality through recipe briefs, sensory standards, traceability, batch acceptance, packaging and supplier audits.

LOCK CURRENT CAPABILITY

Known in-house

Kesar shrikhand · ukadiche modak · puranpoli · sheera · gulabjamun · current menu desserts

WHYProtect controllable strength first. Culinary validates recipe, yield, hold, safety, outlet finish and production ownership.

VALIDATE SIMPLE ADDITIONS

Familiar-process products

Narali bhaat · amrakhand · kharvas · tilgul · gul poli · seasonal basundi

WHYPotentially compatible with wet-kitchen, steaming, chilling and controlled batch processes; equipment and shelf life still require trials.

OUTSOURCE FIRST

Complex faral + mithai

Chakli · chivda · karanji · anarse · ladoos · shankarpale · kadboli · bhakarwadi · specialist pedas

WHYAvoid premature capex and rare-skill dependency. Use approved partners under Sanataa specifications and incoming QC.

LIMITED R&D DROP

Story-rich Marathi specials

Puranachi dind · satori · dink ladoo · sunthawada · regional grain and coconut specials

WHYUse preorder and limited quantity to test demand before converting any story into permanent complexity.

01

At-order add

Chaas, chaha, coffee, chutney or sweet attached to the meal occasion.

02

Exit shelf

Thecha, bhajani, papad, chivda or a small sweet pack seen before leaving.

03

Family bundle

Meal components sized and packed for the home, not discounted randomly.

04

Calendar preorder

Capacity-led booking for upvas, festivals, faral, modak and puranpoli.

05

Gifting ladder

Fixed good/better/best hampers plus corporate customisation after supply proof.

Specialist boundary · when outside expertise is required

Product and kitchen specialists

Authentic sweets expertise, frying systems, shelf-life development and specialist sweets-kitchen design may be commissioned if the validated range justifies it.

Labelling and compliance

Packaged retail may require accredited nutritional analysis, nutrition labelling, allergen review, FSSAI label compliance and shelf-life validation. These are specialist deliverables coordinated by TSF and contracted by Sanataa.

13
THE PRODUCT MUST TRAVEL WITHOUT LOSING ITSELF

Client recipe.
Scalable operating truth.

Culinary is an integrated TSF workstream. Its first agenda is to establish the product base for the Central Kitchen and the fresh-to-outlet execution model.

01 · CLIENT

Recipe truth

Ingredients, quantity, method, yield, shelf life, product-cost basis and founder quality cues.

02 · CULINARY

Scale + script

Convert small-batch knowledge into balanced, repeatable batch standards and critical controls.

03 · CK

Prepare in parts

Bases, semi-finished components, batch packing, labelling, QA and dispatch.

04 · OUTLET

Finish fresh

Defined mise-en-place, assembly, cook/finish, hold and service method at outlet level.

05 · LOOP

Measure + correct

Yield, waste, sensory quality, timing, guest feedback and retraining inform the next standard.

Batul · Culinary Lead

  • Own recipe standardisation logic and culinary validation.
  • Approve CK-versus-outlet process breakup.
  • Define sensory, yield, holding and training standards.
  • Guide festival and seasonal curation.
  • Recommend specialist third parties where required.

Chetan · Culinary Execution

  • Run batch trials, timing, yields and documentation.
  • Build process sheets, prep controls and training aids.
  • Test packing, hold, reheat, dispatch and outlet finish.
  • Support physical food trials and launch troubleshooting.
  • Maintain issue logs and revision evidence.
60
days

Seasonal and festival drops are prepared as a cumulative trial cycle every two months. Culinary shortlists the next window, proves product and process, confirms supply and capacity, trains the operating team, and hands an approved brief to Leonid for communication. Nothing is advertised before Culinary and Sanataa approve the product truth.

Integrated team note · what Culinary is accountable for before launch

Base system

  • Recipe master and version control
  • Batch scale matrix and yield sheet
  • CK/outlet responsibility split
  • Critical quality and food-safety controls
  • Packaging, holding and dispatch rules

Transfer system

  • Physical trials and acceptance record
  • One experienced Sanataa person paired with one new person
  • Current production chef moved into a defined CK role
  • Training aid, audit sheet and sign-off
  • Post-launch correction cycle
THE INVISIBLE INFRASTRUCTUREMeeting record

Roles before rush.
Records before scale.

CLIENT LEADERSHIP

Isha + Varsha ji

Decisions, finance, recipe source, product approval, operating ownership and appointment of every employee and vendor.

NON-NEGOTIABLE ROLE

Storekeeper / Project Coordinator

Multiple quotations, purchasing, receiving, stock, site evidence, contractor coordination, supply chain and on-ground escalation.

CONTROL ROLE

Dedicated Accountant

Sanataa-only records, commitments, payments and triplicate documentation: POS record + vendor invoice + challan; liaison with filing CA.

OPERATING OWNERS

Production + Outlet Leads

Recipes, food safety, shift ownership, training, dispatch, stock discipline, service rehearsals and daily performance.

Old × new pairing

One experienced Sanataa team member works with one new team member to transfer product knowledge while making accountability visible.

PetPooja activates at launch

Recipe costing, inventory, stock count, wastage and variance become Stage 2 operating controls once CK and outlet data exist.

Client remains employer

TSF designs roles, scorecards and selection support. Sanataa appoints, directs, pays and manages every employee.

People risk · why the organisation cannot be hired at the end

Founder dependence is the largest risk.

If every item can only be made correctly by Varsha ji, CK and Outlet 2 are not yet scalable assets. Recipe transfer, batch proof and operating ownership must begin before fit-out creates pressure to launch.

Roles follow readiness.

Accounts and project coordination start early; production and food-safety leadership before trials; store/logistics before transfers; outlet manager and team before mock service. Hiring is tied to work, not titles.

15
THE BUSINESS MANAGEMENT & EXPANSION OFFICE

One programme.
Held together.

TSF’s deliverable is not a list of introductions. It is the sustained management of decisions, dependencies, specialist briefs, evidence and readiness across the transformation.

TSF will

  • Run two structured governance meetings per month.
  • Set monthly goals and review planned versus actual.
  • Provide virtual guidance between meetings.
  • Own the programme plan, decision log and dependency map.
  • Translate the concept into culinary, outlet, CK, people, technology and brand briefs.
  • Review specialists and recommend action objectively.
  • Design roles, scorecards, recruitment filters and reporting architecture.
  • Apply SureShot versus R&D discipline and readiness gates.
  • Build the launch, stabilisation and replication decision room.

Sanataa will

  • Provide timely decisions, recipes, data, access and named owners.
  • Appoint and pay employees, vendors, contractors and specialists.
  • Own property, capex, statutory, purchasing and operating commitments.
  • Maintain an empowered Storekeeper and dedicated accountant.
  • Release Varsha ji’s time for recipe transfer and product approval.
  • Operate the CK and outlets under the approved standards.
  • Escalate deviations and share actual operating data.
2×

Governance meetings

Decisions, risks, dependencies and next month’s outcomes.

1×

Monthly scorecard

Planned versus actual, blockers, owners and due dates.

Live

Decision register

One instruction trail across client, TSF and specialists.

Gate

Capital release

No irreversible commitment before the relevant readiness proof.

Scope mechanics · SureShot versus R&D

SureShot

Established needs with a known output and acceptance condition: role descriptions, decision registers, recipe templates, measured layouts, compliance checklists, standard reporting and launch rehearsals.

R&D

Questions that require testing before commitment: hero products, make/buy range, subscription demand, open versus AC performance, table-sharing behaviour, calendar drops and equipment justified by product demand.

ONE BRIEF · CLEAR ACCOUNTABILITYWorking RACI

Specialists contribute.
TSF integrates.

Batul and Chetan operate as TSF’s integrated Culinary function in the client programme. Leonid is introduced after sign-up under its separate specialist proposal. Sanataa retains all owner, employer and contracting authority.

Dhiraj · TSF

Engagement direction, governance, programme integration, operating brief, decision room and client recommendation.

Batul · Culinary

Recipe, product, CK/outlet process, sensory standard, trials, training and specialist culinary judgement.

Chetan · Culinary

R&D execution, batch evidence, documentation, operating tools and launch-floor product support.

Leonid

Audience, brand, content, local discovery, owned-audience journeys and distribution campaigns after approved product truth.

WorkstreamTSFCulinaryLeonidSanataa
Governance, positioning, sequence and readinessRCCA
Menu architecture, recipes, yields, SOPs and trialsCRIA
CK ↔ outlet operating and equipment briefRRIA
Calendar × Drops distribution programmeRCRA
Make/buy, supplier standard and product QARRIA
Roles, recruitment process and reporting designRCIA
Hiring, contracting, statutory, capex and daily operationsCCIA/R
Launch readiness and replication memoRRRA
Internal team commercial boundary

Culinary is integrated client-side.

The client receives one TSF programme and one integrated direction. Batul and Chetan’s effort is scoped and charged internally to TSF as a specialist workstream, with agreed trial days, deliverables, revision limits, consumables and launch-support days.

Specialists remain clearly bounded.

Nutrition labs, sweets experts, kitchen designers, architects, compliance specialists and Leonid may hold their own proposals or contracts. TSF connects their output to one approved brief; it does not conceal scope, cost or accountability.

17
FROM ALIGNMENT TO EVIDENCE

Six months.
Six jobs.

The sequence is a working programme, not a date promise. Dependencies can overlap only when one does not require an unresolved output from another.

MONTH 0101

Align + define

  • Engagement pathway
  • Decision register
  • Concept approval
  • Source + data room
  • Specialist briefs
MONTH 01–0202

Product truth

  • Recipe collection
  • Batch scripting
  • CK/outlet breakup
  • Make/buy shortlist
  • Trial plan
MONTH 02–0303

Validate assets

  • CK technical brief
  • Locality fieldwork
  • Measured property test
  • Dimensional outlet model
  • Capital evidence
MONTH 03–0404

Appoint + build

  • Specialist coordination
  • Storekeeper + accounts
  • Production leadership
  • Procurement controls
  • Content runway
MONTH 04–0505

Trial + train

  • Batch trials
  • Team pairing
  • Pack / dispatch proof
  • Mock service
  • Launch checklist
MONTH 05–06+06

Launch + stabilise

  • Controlled opening
  • Daily issue room
  • Recipe variance
  • Demand learning
  • Replication memo
Dependency rule · what can and cannot overlap

Can overlap

Recipe collection, brand discovery, people-role design, CK due diligence and locality fieldwork can begin once the concept and owners are approved.

Cannot be rushed

Equipment before product decomposition; final outlet visual before a measured site; public product claim before Culinary sign-off; launch before licensing, trials, people and mock service; replication before stabilised evidence.

THE COMMERCIAL CASEWorking model · not guarantee

Profit is designed.
Then proven.

10–20%NET-PROFIT AMBITION

Five controls create the corridor.

  • Product mix protects contribution, not just gross sales.
  • Recipe, purchasing, yield, waste and variance protect food cost.
  • Counter service, CK support and daypart load shape labour.
  • Direct, dine-in, takeaway and aggregator mix shape commissions.
  • Property, fit-out and operating overhead stay inside a verified unit model.
₹15LMONTH 1 WORKING FLOOR

Initial all-channel scenario for team, capacity and cash planning.

₹22LMONTH 3 WORKING GATE

Signals whether awareness is becoming repeat and channel productivity.

₹30LMONTH 6 SCALE GOAL

Equivalent to the ₹1 lakh/day ambition; replication still needs quality and profit proof.

Gross salesBy product, daypart and channel
−
True operating costFood, labour, channel, occupancy, waste, overhead
=
Verified net profitAfter actual costs—not a top-line percentage assumption
Finance workbench · inputs required before any promise

Unit model inputs

Recipe-wise food cost, net yield, wastage, payroll and productivity, site occupancy, utilities, technology, packaging, aggregator commissions, discount funding, marketing, maintenance, depreciation/finance treatment and owner drawings policy.

Capital boundary

This proposal intentionally does not divide the capital between CK and outlet, quote property rents, or issue an equipment BOQ. Multiple capital frames have appeared across discussions and must be reconciled against the approved concept, recipes, measured properties and readiness research after sign-up.

19
PROVE THE MACHINE · THEN COPY IT

Expansion is not
another address.

Replication begins when the model can deliver product, experience and contribution through the team and system—not when the first launch photographs look successful.

G0

Definition

Positioning, menu base, decision rights, scope and research briefs approved.

G1

Product proof

Recipes, yields, make/buy, packs, holds, CK/outlet breakup and training standard validated.

G2

Format proof

Measured 650–850 sq ft model, channel flows, equipment and people plan approved.

G3

Launch ready

Licences, people, technology, stock, service, content and rehearsals pass checklist.

G4

Replication

Six months of repeat, contribution, quality, team ownership and local demand justify the next unit.

RevenueGross sales by channelContributionAfter product + channel costRepeatCustomer and household returnQualityComplaints, reviews, audit passThroughputOrder-to-serve + capacityFounder-freeTeam owns the standard
Replication memo · the actual go / hold / stop decision

Go

Product consistency, contribution, demand, people ownership and CK service levels are stable enough to be transferred; site learning is documented; next-unit format is intentional.

Hold or stop

Founder intervention remains daily, repeat is weak, contribution depends on discounts, complaints persist, CK service is unstable, the team cannot close stock/variance, or the next capital commitment would weaken operating resilience.

THE DECISION ROOMGreenlight the logic

Decide the direction.
Keep assumptions visible.

APPROVE IN PRINCIPLE

The direction

  • Sanataa Marathi Kitchen positioning.
  • CK → Borivali flagship → Dahisar sequence.
  • Fast-casual counter + token + runner service.
  • Separate beverage flow.
  • Integrated TSF + Culinary workstream.
  • Calendar × Drops as distribution logic.
CLIENT DECISIONS TO CLOSE

The mandate

  • Embedded retainer or defined first project.
  • Named decision owners and response times.
  • Capital frame to be reconciled.
  • Varsha ji’s recipe-transfer calendar.
  • Storekeeper and accountant appointments.
  • Leonid introduction after sign-up.
VALIDATE AFTER SIGN-UP

The evidence

  • CK technical, capex and equipment plan.
  • Locality fieldwork and property proof.
  • Dimensionally accurate outlet model.
  • Recipe cost, shelf life and make/buy.
  • Launch channel and subscription pilot.
  • 10–20% net-profit unit model.
01

Dimensionally accurate outlet visual

Open Points · Internal

02

Three launch hero products

Open Points · Internal

03

Final in-house versus outsourced mithai / farsan list

Open Points · Internal

04

Exact CK / outlet capital allocation and equipment plan

Open Points · Internal

05

Subscription owner, service radius, slots and economics

Open Points · Internal

06

Launch-channel decision and exact Borivali locality

Open Points · Internal

DHIRAJ’S RECOMMENDATION

Do not rush
to look bigger.Become easier to repeat.

Approve the Marathi Kitchen direction, the asset sequence and the integrated TSF scope. Then convert every remaining assumption—recipe, property, layout, equipment, team, demand and economics—into operating evidence. Sanataa expands when the first new model can perform without founder heroics.

Review decisionsBack to cover
GOVERNING

Scope of Work Meeting — Sanataa Snacks · content before “Concept Design & Proposal Content is below.”

PRODUCT

Client final menu dated 26 August 2026, as summarised in the project knowledge base.

MODELLING

TSF concept design and Base Project Knowledge File v2.0.

SPECIALIST

Leonid Strategic Partner Brief v2 · only the two marked distribution sections integrated.