# 28 — Competitive positioning & ICP workbook

**Go Past Earth — Overhead and Operations (OAO)**  
**Audience:** CEO, product, sales, solutions engineering  
**Purpose:** Stay grounded when comparing this platform to **suite-scale** competitors (Lightspeed-class: broad retail/restaurant OS + ecosystem). This is a **living** document: copy the tables into Notion or a deck, fill them honestly, and refresh at least quarterly.

**Related:** [00 — CEO Strategic Overview](./00-CEO-STRATEGIC-OVERVIEW.md) (vision and headline positioning), [25 — Platform coverage](./25-platform-coverage.html) (what exists in code vs aspirational).

**Browse (HTML):** [28-competitive-positioning-and-icp-workbook.html](./28-competitive-positioning-and-icp-workbook.html) — same content with OAO nav and styling.

---

## 1. Three lenses (use these before roadmap panic)

### 1.1 Coverage vs depth

**Suite competitors optimize for breadth:** many workflows are “good enough” and completed through **integrations** (accounting, payroll, ecommerce, loyalty vendors, marketplaces).

**You may legitimately choose depth:** fewer workflows, owned end-to-end (POS, invoicing backbone, tenant model, inventory, Bridge, crypto, etc.). That is a **strategy**, not evidence that the company is “not real.”

**Decision rule:** If your *ideal customer* can run their week without duct tape in the areas you claim, breadth gaps elsewhere are often **integrate** or **defer**, not existential.

---

### 1.2 Ecosystem gravity

What people feel as “Lightspeed is complete” is often **distribution and trust**, not only software:

- Certified hardware and payment **device** narratives  
- Payment **rails** and acquiring relationships  
- **App marketplaces** and accountant/bookkeeper familiarity  
- Brand recall in RFPs and banks

That gravity is built with years of partnerships and marketing. It is **not** the same task list as “finish the POS API.”

**Decision rule:** Separate “we need feature X for parity” from “we need partner Y or certification Z for trust in channel C.”

---

### 1.3 Enterprise table stakes

For **larger** deals, buyers often weight artifacts that sit **beside** the POS:

- Security posture and **SOC 2** (or roadmap + controls narrative)  
- **SLAs**, support tiers, escalation paths  
- Formal **onboarding**, migration assistance, training  
- Procurement-friendly **contracts**, DPAs, subprocessors list

These are **often separate workstreams** from core product engineering. Missing one in early stage is normal; missing it on a deliberate **enterprise** push is a gap to plan, not a reason to doubt the whole product.

---

## 2. Ideal customer profile (ICP) — one sentence

**Template (copy and edit):**

> We win with **[vertical or business type]** at **[size band: locations, seats, GMV, headcount]** who care most about **[primary pain: speed, cost, crypto, multi-site ops, compliance, etc.]** and who are frustrated by **[incumbent or workaround]**.

**Your live ICP (fill in):**

> We win with _________________________________________________  
> at _________________________________________________________  
> who care most about _________________________________________  
> and who are frustrated by ____________________________________.

**Anti-pattern:** “Everyone from food truck to enterprise” — impossible to sell, prioritize, or document honestly.

---

## 3. Top ten *daily* workflows — comparison matrix

Use this against **any** suite (Lightspeed, Toast, Clover, Square for Retail, etc.). The third column is **your** honest read of Go Past Earth today; replace with checked facts as the product moves.

**Column `Gap tag`:**

| Tag | Meaning |
|-----|---------|
| **must-build** | ICP cannot operate without it; build in-platform or it blocks revenue. |
| **integrate** | Standard to buy/partner (accounting, payroll filing, shipping labels, etc.). |
| **defer** | Nice for parity; ICP does not need it in the next two quarters. |
| **not our market** | Deliberately out of scope; say no in sales. |

| # | Daily workflow | “Good” in a mature suite | Go Past Earth (directional) | Gap tag (edit) |
|---|----------------|------------------------|-----------------------------|----------------|
| 1 | Open store / open register / start shift | Fast, role-based, audit trail | POS + register/shift flows; admin open registers | *fill* |
| 2 | Sell line items + modifiers + tax | Reliable, offline-tolerant where promised | Multiple POS surfaces; invoicing backbone; tax module | *fill* |
| 3 | Take payment (card/cash/wallet/gift) + receipt | Certified devices, clear declines | Payments engine + receipts + gift cards; crypto distinct | *fill* |
| 4 | Return / void / manager override | Permissions, audit | POS + audit taxonomy; tighten with RBAC story | *fill* |
| 5 | Receive or adjust inventory | POs, counts, transfers | Inventory + vendors + ledger; multi-location as you scope | *fill* |
| 6 | Clock in / schedule / basic labor | Timeclock, exports to payroll | HR + timeclock + Business Center paths | *fill* |
| 7 | End of day / Z-style close | Registers, reconciliation, exports | Register close + reporting; align narrative to accounting export | *fill* |
| 8 | See yesterday’s sales / margins | Dashboards, exports | Analytics + reports; depth varies by module | *fill* |
| 9 | Serve booked or walk-in service jobs | Appointments + tickets | Tickets & appointments | *fill* |
| 10 | Omnichannel hook (web order, pickup) | Ecom sync, menu sync | Storefront + platform patterns; compare to ICP need | *fill* |

**How to use:** In a working session, read each row aloud. If the ICP sentence (section 2) is true, **only `must-build` rows** are allowed to block positioning for that segment.

---

## 4. Suite checklist without losing the plot

When a competitor ships a **module** you do not have, run it through this order:

1. **Does my ICP use it weekly?** If no → `not our market` or `defer`.  
2. **Is it a commodity integration?** If yes → `integrate` (document partner, not rebuild).  
3. **Is it trust / procurement?** If yes → enterprise table stakes (section 1.3), often parallel track.  
4. **Only then** → `must-build`.

---

## 5. Review cadence

| When | Do this |
|------|---------|
| Quarterly | Update section 2 (ICP) and the gap tags in section 3. |
| Before a fundraise or large pilot | Add a one-pager: three lenses + ICP + top 3 `must-build` items only. |
| After a major release | Reconcile section 3 with [25 — Platform coverage](./25-platform-coverage.html). |

---

## 6. Summary

Being smaller than a public suite is **not** the same as being incomplete. **Completeness for your ICP** is the bar. Use **coverage vs depth**, **ecosystem gravity**, and **enterprise table stakes** to sort anxiety into either product work, partnership work, or narrative work — then execute the smallest honest slice.