startups as

Approvals.Email approvals.email

on-stagehouse

The approval that lives in email anyway, made trackable and non-forgettable: the approver replies in the thread, and the decision becomes a record of who decided what, when, from which message.

From the Startup card at api.sb/approvals.email · Designed · App.

What it is

Tier	house	Inferred · low · portfolio-lens-a.tsv (tier)
Status	on-stage	Inferred · low · lens A stage next400
Product kind	—	no provenance
Core noun	—	no provenance
Buyer and position	Deliverable Mint: "approvals"	Inferred · low · portfolio-lens-b.tsv (icp_or_position)
Closed set or journey	Email task rails · approvals	Inferred · low · portfolio-lens-a.tsv (set_or_journey)
Abstraction	B-comms	Inferred · low · portfolio-lens-b.tsv (abstraction)
Role (lens B)	projection	Inferred · low · portfolio-lens-b.tsv (role)
Registrar	dynadot	Inferred · high · holdings ledger (domains repo, read-only)

Its stack

Generated around Approvals.Email

                                         Approvals.Email                                                    centre
                                                │
                                       StartupBuilder.Dev                                                   brands
                                                │
           Startups.Management ───────── Startups.Studio                                                    the factory
                           ╱             ╱      │      ╲             ╲
  SaaS.Dev                MonthEnd.Finance Objects.do    Services.do                 Workers.do             the foundation · Do.Industries
             ╲             ╱                           ╲
               Headless.ly                                          Gigs.Accountants                        the abstractions
                                  ╲
                                           SaaS.Studio                                                      the abstractions

Click any node to re-centre the stack on it; the trail above keeps the nesting. Each node's own page is one more click.

Neighbours

Same abstraction (B-comms)

Address.do Addresses.do Calls.do Emails.do Escalate.do Escalations.do Followup.do Numbers.do Texts.do Delegations.Email Drips.Studio Emails.Studio Recaps.Email Reminders.Email Rewrites.Email Summaries.Email Svcs.Email

Listed by

no discovery view lists it yet

In logo rows

StartupBuilder.Dev's row specified
Headless.ly's row buildable
API.SB's row runs today

Slices

in no slice

Relationships (3)

from	verb	to	provenance
Approvals.Email	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	StartupBuilder.Dev	Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified sb/poc/startup-as-noun/defs/approvals.email/startup.data.mdx
Approvals.Email	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	Headless.ly	Inferred · low · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvbuildable sb def approvals.email: built on headless.ly [low] — Stated by r4-domains; an approval is a record on the business-systems runtime. No production call recorded.
Approvals.Email	runs-on logo row: "Powering" / "Built on" (customer runs on supplier)	API.SB	Inferred · high · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvruns today api.sb/approvals.email answers (status Designed, fetched 2026-10-24)

Edit log

loading the versions of this record from api.sb…

Machine-readable: /approvals.email.json