Real run

Positioning Memo Builder

Sample 1 · 2026-10-29 · Grok Bot executor subagent (model family not disclosed)

Bot page

Positioning statement

For owners of a single cafe who ran out of stock before Tallyhaus [E2] and want stock counts that take minutes [E4], Tallyhaus is an inventory and reorder app that counts stock from shelf photos [product facts, E4]. Unlike spreadsheets and clipboards [E1], it suggests reorder quantities from the last 8 weeks of sales [product facts, E5].

Target segment

Segments use the labels exactly as they appear in your evidence. No labels are merged.

Segment (role, company type, as labeled) Evidence lines Count
Owner, single cafe E2, E4 2
Owner, 2 location cafe E1 1
Owner, 3 location cafe E5 1
Operations manager, 6 location group E3 1
Total 2 + 1 + 1 + 1 = 5

Top segment (derived from the evidence, no hint supplied): Owner, single cafe, with 2 of 5 lines. No other label reaches 2, so there is no tie.

Alternatives

Alternative Confirmed facts Source
Spreadsheets and clipboards An owner did counts "on a clipboard every Sunday night" E1
MarketMan Plans listed for restaurants; starting price shown on request MarketMan pricing page, opened October 2026 (as you supplied)
Doing nothing, ordering by feel No facts supplied None

No weakness is claimed for MarketMan. The only sourced facts are its restaurant listing and that its price is on request.

Unique attributes and proof

"Unique" here means stated for Tallyhaus and not stated for any alternative in your input.

Attribute Proof Status
Counts stock by scanning shelf photos E4 (Owner, single cafe): "Photo counts take me ten minutes now." Supported
Reorder suggestions from the last 8 weeks of sales E5: "Reorder suggestions are right most weeks, I still tweak them." Supported. E5 says the owner still adjusts them, so do not call them automatic or always right.
Square POS integration E3: "The Square sync means I stopped exporting CSVs." Supported, but from the operations manager line, not the top segment
Published price of $59 per location per month, where MarketMan shows price on request Product facts; MarketMan pricing page Supported as a fact. "Cheaper" would need MarketMan's actual price.
Built for coffee shops Product facts [ADD: proof, such as cafe specific features]

Public proof point: 410 cafes use Tallyhaus.

Value themes

Each theme is named in a customer's own words.

  1. "Photo counts take me ten minutes": less time on stock counts (E4, top segment; E1 describes the clipboard routine it replaces).
  2. "We ran out of oat milk": fewer stockouts (E2, top segment). One customer's experience; there is no measured stockout rate.
  3. "I stopped exporting CSVs": no manual data moves through the Square sync (E3).

Gaps and open questions

  • The top segment rests on 2 lines. Every other label has 1. More single cafe evidence would make the choice firmer.
  • E1 (2 location) and E5 (3 location) are separate labels with 1 line each. If multi location owners matter, collect more lines from each size before targeting them.
  • Only 1 line comes from an operations manager (E3), so the Square sync theme is thin for the top segment.
  • The MarketMan comparison rests on its pricing page only. A feature comparison would need sourced facts about MarketMan.
  • "Doing nothing" has no supporting facts. A quote about ordering by feel would let the memo address it.

Needs your decision

  • The product lead approves this memo before anyone uses it.
  • Get permission from each quoted customer before public use.
  • Fill in the [ADD: proof] placeholder for "built for coffee shops", or drop that attribute.