Pitch Deck Narrative · Pre-Seed 2026

Kettlewise

Inventory autopilot for independent cafés: "Order tomorrow's milk, pastries, and beans in one tap."

Company

Kettlewise Inc.

Portland, OR

Raising

$750K pre-seed

Stage

Early revenue

How to use this narrative

This is the story your deck needs to tell, written slide by slide. Each slide has a headline (the one sentence the investor should remember), body copy, and speaker notes in your voice. Where your materials have a gap an investor will find, there is a flag on that slide. The flags are part of the deck work. Several of them will come up in the first ten minutes of a real pitch meeting.

Narrative arc. The deck moves in five beats:

1. The painOrdering by gut feel, paying for it twice

2. The fixForecast, draft, approve in one tap

3. The proofPilot, paid conversions, waitlist

4. The why-usOperators plus a forecasting engineer

5. The ask$750K to prove repeatable acquisition

The single biggest structural risk in this deck: beat 3 to beat 5 has no bridge. You have 4 paying cafés and a target of 300, and your materials describe no way to get from one to the other. Investors at pre-seed back founders who have a believable answer to "how do you get customers." Slide 11 below builds the strongest go-to-market hypothesis your materials support, but you have to validate it and put real numbers on it before this deck is ready.

Slide 1Title

Kettlewise: order tomorrow's milk, pastries, and beans in one tap.

Inventory autopilot for independent cafés. Kettlewise Inc. · Portland, Oregon · Pre-seed 2026.

Visual

A phone in a café owner's hand at 6am showing a drafted order with a single "Approve" button. No dashboards and no charts. The product's promise is that the owner doesn't need either.

Speaker notes: "We're Kettlewise. We ran cafés, and the worst part of every week was ordering. So we built the tool we wanted. It drafts every supplier order for you, and you approve it in one tap."

Slide 2The Problem

Independent café owners order by gut feel and throw the difference away.

A typical owner places 4–6 supplier orders a week from memory and a clipboard. Every order is a guess, and the guess costs money in both directions:

Over-order: unsold pastries and spoiled milk go in the bin at close.
Under-order: the oat milk runs out at 10am and the regulars walk.

We interviewed 14 Portland café owners. 12 said ordering is the most stressful part of their week.

Visual

A split image: a bin of day-old pastries at close on the left, an empty oat milk shelf at 10am on the right. Caption: "Same café. Same week."

Speaker notes: Lead with the 10am oat milk moment, ideally from the CEO's own nine years running cafés. "When I was running three locations, I'd find out we were short when a regular asked for an oat latte and we couldn't make it. Then at close I'd throw out croissants I'd paid for that morning. That happened every week, at every location."

Flag: the problem has no dollar figure. "Most stressful part of the week" shows the pain is real, but investors need to know what it costs. Before you pitch, get a dollar range for weekly waste and lost sales per café. Use pilot data, or ask your 4 paying cafés directly. Without that number you can't defend the $79 price on Slide 8. Also, 14 interviews all in Portland is a reasonable start, but expect the question "is this a Portland problem or a national one?"

Slide 3Why Independents Get Left Behind

Chains have forecasting teams. The corner café has a clipboard.

Multi-site groups use restaurant inventory platforms that are priced, staffed, and configured for operations with a back-office. The corner café owner is the buyer, barista, bookkeeper, and inventory manager, often in the same hour. The tools they have today fall into two buckets:

Free but blind: spreadsheets and clipboards. No forecasting at all.
Counts but doesn't think: built-in POS inventory tracks stock levels. It doesn't predict demand or draft an order.

The gap is a tool that does the thinking and the ordering, sized for a 20–40 item menu and an owner with no time.

Speaker notes: "Nobody has ignored this market on purpose. Enterprise tools are expensive to sell and support, so vendors go after chains. The independent owner ends up with either nothing or a tool built for someone with an operations team."

Flag: "Small menu" is your claimed edge, and right now it is an assertion. Be ready to explain specifically why forecasting a small menu is different. One possibility is that sparse data per item makes generic models perform badly. If that's true and your CTO can explain it in two sentences, this slide gets much stronger. If it isn't true, drop "tuned to small menus" as a differentiator.

Slide 4The Solution

Kettlewise drafts every supplier order. You approve it in one tap.

Connect your point-of-sale system (Square and Toast today). Setup takes 20 minutes, with no spreadsheets.
Forecast: Kettlewise predicts demand per item using your sales history, weather, and local events.
Draft: each supplier order is pre-built for you: milk, pastries, beans.
Approve: one tap from your phone.

Visual

A four-step horizontal flow with phone screenshots for steps 3 and 4. A live 30-second demo here is stronger than any static image.

Speaker notes: "The owner never builds a forecast or fills in a spreadsheet. They wake up to a drafted order and decide whether they agree. Most mornings they do."

Flag: two open questions an investor will ask within a minute. (1) Where does the weather and local-events data come from? Name the source, or say plainly that it comes from a third-party API and what it costs you per café. (2) What happens after the owner taps "approve"? Does the order go directly to the supplier, go out by email, or get handed back to the owner to place? This matters a lot. If Kettlewise transmits orders, "one tap" is real and you have a path to the supplier revenue on Slide 8. If the owner still has to call or email the supplier, then "one tap" overstates the product and the pitch line needs to change. Don't present this slide until you can answer both questions in one sentence each.

Slide 5Why Now

Café sales data is finally digital, and forecasting is finally cheap.

Cloud POS is now standard for independents. Square and Toast put item-level sales history into an API, which an outside product can read with the café's permission. A decade ago that data sat on a register tape.
Demand forecasting has become commoditized for large operators. Your CTO built it for 200+ grocery stores. The methods exist. What's missing is a version packaged for a single-location owner at a price they'll pay.
Margin pressure on independents. Rising ingredient and labor costs make waste more expensive.

Speaker notes: Keep this short, about 30 seconds. The strongest point is the first one, because it explains why nobody could build Kettlewise for independents five years ago.

Flag: The margin-pressure point is directionally reasonable, but your materials don't include a source for it. Either cite a specific industry figure or cut the bullet. An unsourced macro claim weakens the sourced claims around it.

Slide 6Traction

8-week pilot with 6 cafés. 4 converted to paid. 120 on the waitlist.

Portland pilot cafés, 8 weeks

4 of 6

converted to $79/mo paid

31%

less pastry waste (owner-reported)

120

cafés on waitlist

At 4 paying locations, Kettlewise has roughly $316 in MRR (monthly recurring revenue, the subscription income you can expect each month). The product is live and in daily use.

Speaker notes: "We didn't give the product away and hope. We ran a structured pilot, and at the end of it two-thirds of the cafés pulled out a card and paid full price. Pilot owners reported cutting pastry waste by about a third."

Say "owner-reported" yourself, before the investor asks. Volunteering that limit earns more trust than an investor discovering it.

Flag: every number on this slide invites a follow-up, and right now you can't answer most of them.

Why did 2 of 6 not convert? This is the first question you'll get. If you don't know, call them this week. Their reasons (price, accuracy, POS issues, supplier mismatch) are some of the most valuable data you have.
31% is owner-reported, pastry only. There are no milk or bean figures. Investors will notice that you have only one of the three products in your pitch line. If you have POS-based before-and-after data, use it. If not, say "owner-reported" on the slide, not only aloud.
The 120-café waitlist has no description. Where did these cafés come from? Where are they? Have any been contacted? An unqualified waitlist is a weak signal, and some investors discount it to zero. If you can say "120 cafés, 40% outside Oregon, 30 have booked a setup call," it becomes real evidence. If you can't, consider showing it smaller than the paid figure.
Lead with the paid figure, not the waitlist. Four cafés paying full price is your strongest evidence. Make it the largest number on the slide.

Slide 7Market

38,000+ US independent coffee shops: a $36M+ core market, with a much larger adjacent one.

Layer	Definition	Size
Core	US independent coffee shops × $79/mo × 12	~$36M/yr
Adjacent	Bakeries, juice bars, small restaurants with the same ordering pain	Not yet sized
Later	Supplier referral fees on cleaner, predictable orders	Not yet sized

The core figure is built bottom-up, meaning it is calculated from a real count of potential customers multiplied by your actual price, not taken from a broad industry report. That makes it credible.

Speaker notes: "We sized this conservatively from shop count and our real price. Coffee shops are where we prove it. The same ordering problem exists in every small food business that buys perishables several times a week."

Flag: $36M is a ceiling problem, and investors will see it immediately. $36M is the total annual revenue if every independent coffee shop in the US paid you. Realistic share is a fraction of that. Many pre-seed investors need to believe a company can reach $100M+ in annual revenue, and coffee alone can't get there at $79. That makes the expansion layers essential to the pitch. Before presenting this slide, size the adjacent market with the same bottom-up method: count US independent bakeries, juice bars, and small restaurants and multiply by a realistic price. Also find a source for the 38,000 figure and cite it on the slide.

Slide 8Business Model

$79 per location per month. Simple, self-serve, and priced against what waste already costs.

Today: subscription at $79/month per location.
Later: referral fees from suppliers, who benefit from cleaner, more predictable orders. This is not part of the business today.

The ROI line you need

"A café that saves $[X] a week in waste and lost sales gets paid back [Y] times over." Fill this in from real pilot data.

Speaker notes: "$79 is less than most cafés throw out in pastries in a single week." Say this only if your pilot data supports it.

Flag: no unit economics yet. Unit economics are the profit or loss on a single customer. Investors will ask for three numbers: CAC (customer acquisition cost, what you spend to win one café), churn (the share of cafés that cancel each month), and LTV (lifetime value, total revenue from an average café before it cancels). With 4 customers you can't prove these, and nobody expects you to at pre-seed. But you should state your assumptions and how the round will test them. Also: supplier referral fees depend on Kettlewise actually transmitting orders to suppliers (see Slide 4). If you don't transmit them, this revenue stream has no foundation yet.

Slide 9Competition

Today's options either don't forecast or weren't built for one-location owners.

Alternative	What it does well	Where it falls short for the corner café
Spreadsheets & clipboards (status quo)	Free, familiar, fully under the owner's control	No forecasting. Depends on the owner's memory and time.
Built-in POS inventory (Square, Toast)	Already installed, no new vendor, counts stock	Tracks what you have. Doesn't predict demand or draft orders (verify current feature set before pitching).
Restaurant inventory & purchasing platforms (e.g. MarketMan, MarginEdge, Restaurant365, Toast's xtraCHEF)	Deep purchasing, invoicing, and cost control	Generally built and priced for multi-site and full-service restaurants, with heavier setup. Pricing and features for single-location cafés need verification.
Supplier ordering portals and apps	Direct to the supplier, often free	One supplier at a time, no cross-supplier forecasting

Speaker notes: "Our biggest competitor is the clipboard. Our most dangerous competitor is the POS itself, and here's why we think we win anyway." Then go to Slide 10.

Flag: name competitors on the slide. Your deck currently names only categories. Investors read that as either not knowing the space or hiding it. The products listed above are ones I'm reasonably confident operate in restaurant inventory and purchasing, but I'm not certain about their current features or small-café pricing, and product capabilities change. Check each one directly before this goes in front of anyone. Pay particular attention to Toast: xtraCHEF sits inside a POS you integrate with, and Square could build forecasting into its own inventory. If either has added demand forecasting or auto-ordering, this slide must say so.

Slide 10Why We Win

Forecasting built for small menus, one-tap ordering, and a team that has lived the problem.

Small-menu forecasting: tuned for low-volume, perishable-heavy menus where generic models struggle (to be substantiated, see Slide 3 flag).
One-tap supplier orders: the product finishes the job instead of handing the owner a report.
Operator credibility: a CEO with 9 years in café operations sells to café owners as a peer.

What compounds over time

Every café adds sales, waste, and ordering data across items, suppliers, weather, and neighborhoods. Over time, that dataset could make Kettlewise's forecasts for a new café accurate from day one, which a POS vendor's general inventory tool would not prioritize.

Speaker notes: Expect the question: "If Square or Toast built this tomorrow, what stops them from catching up in 18 months?" Answer with the data argument and the supplier relationships, not speed. "We'll move faster" is not a moat, and investors know it.

Flag: as written, none of the three advantages is a durable moat yet. A well-resourced POS company could build small-menu forecasting and order drafting. Operator credibility helps you sell, but it doesn't stop a competitor. Your strongest potential moats are (a) a cross-café forecasting dataset and (b) direct supplier integrations that are slow and relationship-heavy to replicate. Both are currently future-tense. Present them as the thesis the round will test, not as advantages you already have.

Slide 11Go-to-Market

From 4 to 300: three channels we will test in the first six months.

Your materials contain no go-to-market plan. The channels below are hypotheses built from what you do have. Each one has to be tested and backed with early numbers before the deck is ready.

Channel	Why it fits Kettlewise	What to prove
1. Waitlist conversion	120 cafés already raised their hand	What share book a setup and pay within 30 days
2. POS app marketplaces (Square, Toast partner listings)	Owners already looking for add-ons in a tool they trust. Integration is already built.	Listing approval, install-to-paid conversion
3. Operator-led local density	CEO's café network. Owners in a city talk to each other and often share suppliers.	Referral rate from paying cafés, cost per acquired café in one new city
Later: supplier channel	Distributors who benefit from cleaner orders could recommend Kettlewise to their accounts	Depends on order transmission (Slide 4)

Speaker notes: "Our first 4 customers came from the pilot. The round is about finding the channel that brings in café number 50 at a cost we can repeat. Here's what we've already tested and what we've learned." Only say this after you've run at least one test.

Flag: this is the slide that decides the meeting. 300 cafés in 18 months means signing about 16–17 new cafés a month, every month, from a base of 4. That's a big jump with no described channel. Before pitching, run even a small test: email the waitlist and count conversions, or submit to one POS marketplace. One real acquisition data point is worth more than this entire slide written as hypothesis.

Slide 12Team

We ran cafés. Then we built the tool we wanted.

Role	Background	Why it matters
CEO [Name]	9 years in café operations, most recently running three locations	Has placed thousands of the orders Kettlewise automates. Sells to owners as a peer.
CTO [Name]	Former data engineer at a grocery delivery startup. Built demand forecasting for 200+ stores.	Has already built perishable demand forecasting at scale. The core technical risk is one they've solved before.
Advisor [Name]	Former regional manager at a national coffee chain	Knows how chains handle supply and forecasting, and where independents are underserved.

Speaker notes: This is your strongest slide. Operator plus forecasting engineer is the right pairing for this exact problem. Tell it as one sentence: "One of us lived the problem for nine years, and the other has already solved it for grocery."

Flag: Add names and photos. State whether both founders are full-time, because investors will ask and part-time founders at pre-seed are a serious concern. List anyone else working on Kettlewise. If the CEO's three-location experience was at independent cafés rather than a chain, say so explicitly, because it strengthens the "we are the customer" claim.

Slide 13The Ask

Raising $750K pre-seed to prove repeatable café acquisition and reach 300 paying locations.

A pre-seed round is the earliest institutional funding, usually used to prove a product works and that customers can be acquired repeatably.

18-month milestones (from your materials)

300 paying cafés
Two additional POS integrations
Supplier marketplace pilot
Hire one engineer and one café-success lead

Use of funds

Not provided in materials. You need a breakdown here (for example, % to product and engineering, % to acquisition, % to customer success, % to operations) and a stated runway in months.

Speaker notes: "This round gets us to the point where we know exactly what it costs to acquire a café and how long they stay. That's the proof a seed investor needs."

Flag: the milestones are overloaded and partly contradictory.

300 cafés is about $284K ARR (annual recurring revenue: 300 × $79 × 12). That's a real milestone, but it's below what many seed investors expect when the next round comes. Decide whether 300 is the right target, and be ready to defend it.
The supplier marketplace is listed as "later" in your business model, but it's funded in this round. Pick one story. If it's a pilot to validate supplier revenue, say so. If it's later, remove it from the milestones and free up the money for acquisition.
$750K covering two hires, two integrations, a marketplace pilot, and an acquisition engine needs a budget behind it. Two founders plus two hires for 18 months may consume most of the round on salaries before acquisition spend. Build the spreadsheet and show the runway.
Prior funding: state whether there is any. If none, say "first outside capital."

Slide 14Vision and Close

Every small food business deserves the ordering intelligence chains take for granted.

We start with coffee because we know it from the counter. The same 6am guess happens in every bakery, juice bar, and small restaurant that buys perishables several times a week. As Kettlewise learns across thousands of independent locations, it becomes the ordering layer between small food businesses and their suppliers: less waste, fewer stockouts, and an owner who gets their mornings back.

Final line on screen

"Order tomorrow's milk, pastries, and beans in one tap." Kettlewise · [contact]

Speaker notes: End where you started, with the owner at 6am. "We've proven café owners will pay for this. This round proves we can find them repeatably. We'd like you to be part of it." Then stop talking and take questions.

Flag: "The ordering layer between small food businesses and suppliers" is the version of Kettlewise that justifies venture investment, and it depends on supplier integration you haven't described. Don't lean on this vision harder than Slide 4 can support.

Appendix A: Questions to rehearse before any pitch

Why did 2 of your 6 pilot cafés not convert?
When an owner taps "approve," what physically happens to the order?
Where does your weather and local-events data come from, and what does it cost per café?
How was the 31% waste reduction measured, and what happened to milk and beans?
Where did the 120 waitlist cafés come from, and how many are outside Portland?
How will you acquire café number 50, and what will it cost?
What stops Square or Toast from building this?
How do you get past a $36M ceiling?
How is the $750K allocated, and how many months of runway does it buy?
Are both founders full-time?

Appendix B: Fix list before this deck goes out

Run one acquisition test (waitlist email or POS marketplace listing) and put the result on Slide 11.
Call the 2 non-converting pilot cafés and write down why they left.
Answer the order-transmission question. If orders don't reach suppliers automatically, revise "one tap" everywhere.
Put a dollar figure on waste per café to anchor the problem and the price.
Size the adjacent market bottom-up to address the $36M ceiling.
Build a use-of-funds breakdown with runway, and resolve the marketplace-pilot contradiction.
Name and verify competitors, especially POS-native inventory features.
Add team names and full-time status.