manymoatsthe biography

manymoats · the full biography · no account required

You've probably misread us.
Good. That's the story.

Seventeen doors. One house. Scroll.

seventeen properties · one spine underneath, the thesis of this whole page, in miniature

keep going
§1
§1 · The Misconception

What this isn't

Let's say the unflattering thing out loud, because you were already thinking it: from the outside, this can look like chaos, a document signer, a writing tool, a link page, an automation builder, a research engine, a scheduling app, seventeen-odd domains pointed nowhere in particular.

Here's what that read misses: you're not looking at seventeen products. You're looking at one operating system wearing seventeen faces · same account, same wallet, same spine underneath every one of them, each aimed at a different bloated incumbent's most overpriced habit. The company is literally named for the strategy: many moats.

The breadth isn't the bug. The breadth is the coverage. And the spine underneath it is the moat.

live, seventeen doors, one lattice

scroll triggered this once, the same seventeen cards, now snapped into one connected row. no drawn wires; just proximity and alignment.

§2
§2 · The Tour

Every property. Real features.

Receipts on request, this page classifies its footnoted claims, and the drawer at the bottom holds the audit.

filefriend

filefriend.org fill it, sign it, keep it

Blank form to signed, sealed, stored, in one window, forty-one templates, sixteen field types, routed multi-party signing, a seven-year vault.

Every signature writes into a genesis-chained, SHA-256 tamper-evident audit trail · each fingerprint derives from the one before it, so a single function can prove nothing was touched. Checkable, not just claimed.

$4.99 for a document, $2.49 after · no subscription, priced server-side from your real history. Drop in any PDF and on-device field detection makes it fillable, no upload, ever.

syntax

yoursyntax.app find your syntax

A writing OS that lives anywhere you type: @ to summon, / to act. Commands commit on a closing delimiter, not Enter, and the host page locks mid-command, structurally impossible to misfire a submit button while talking to the AI.

The accessibility layer, read-aloud, dyslexia mode, simplify, dictation, is permanently $0, on-device, forever. Pro is $8/month, students $5. That's the whole pricing page.

grepthat

grepthat.com turn any company into receipts

A seven-agent research crew. Navigator, Harvester, Sifter, Cross-Examiner, Analyst, Creative Strategist, Closer, builds a sourced dossier. Cost shown before you commit.

Every claim is classed verified / unverified / could-not-find · that third class is mandatory. A research product that only returns confident answers is lying somewhere; ours can't.

↓ this page's own footnoted claims, classified, in the drawer

gogrepthat

gogrepthat.com the open door

The same research crew, no charge, no login, no email ransom. One question at a time, never a form wall. The door stays open on purpose: it's the best salesman we own.

tethered

tetheredlink.com your page, your money

0% seller fee, and your page is a self-contained link that decodes entirely on the visitor's device, no server between your audience and your page. Built on an infinite canvas with the magic cursor. (Hosted accounts and analytics are next; the builder and the page are the product today, fully yours.)

togglesnap

togglesnap.com automation you can read

Every step wears its function: an email step looks like an envelope, a filter is a funnel, read a workflow at a glance, like a sentence. Fourteen starter templates, a full node canvas, test-runs that animate data node to node. (Live execution is next; the builder says so.)

cohortcollab

cohortcollab.com scheduling with no black box

The Slot Inspector: click any time slot and it tells you exactly why, with a machine-readable reason code · rejected_due_to_buffer_collision, accepted_after_priority_resolution. In the live demo, a booked meeting becomes a pipeline contact on a kanban board instantly, scheduling and CRM as one record. (Calendar sync and payments are next.)

inputdojo

inputdojo.app the anti-form

Forms are where businesses lose people. inputdojo replaces the wall of fields with a conversation, one question at a time, the Pull Law (surface the next right thing, never dump the pile), weaponized against the humble form.

loomallure

describe it, and it builds

Tell the loom what you need; it composes a working interface in front of you · from pre-audited parts only. Why that restriction is the whole invention: next section.

And the bench. yapcircuit (conversation automation) and lathe (artist growth) are named, priced in law, and deliberately queued, a brand launches when its machinery is real, not when its landing page is pretty. synergymade holds an incubator thesis of its own.
§3
§3 · What We Actually Are

The operator's system

Now the real answer.

manymoats is an operator's system: one identity, one wallet, one data spine, one set of laws, rendered as many products.

  • One login across the fleet. Entitlements are decided on the server, never by a flag the page could flip, not a pile of "linked accounts," one identity of record.

  • One wallet. A single credit balance spends across the whole portfolio. No per-product currencies, no tier shaming.

  • One record spine. Your contract on filefriend, your booking on cohortcollab, your research mission on grepthat, all on one shared store, wearing different faces. We don't integrate our products with each other. They were never separate.

  • One pass. The Rail Pass: one subscription that unlocks its tier across the portfolio, live at filefriend today, each additional door wired on the same rail as it ships.

The part we think is genuinely beautiful: the company's beliefs are written as law, and the hardest of the laws are enforced by machines. Sixty-nine codified sections govern everything from pricing floors to the ban on dark patterns, and twelve automated gates and guards stand at the deploy line, scripts that physically refuse to ship a violation. A build that leaks a secret or breaches a floor never becomes an argument, the gate just says no.

We call the doctrine idea vs. thing: the belief, stated plainly, then the mechanism that makes it enforceable. A value that isn't enforced is a poster. Ours compile.

live, one record, four faces

Recordcontract-a118
ClientA.I. Dogfood Storefront
StatusSigned
Amount$4.99

sample record · A.I. Dogfood · same underlying data, four renderings, zero copies

§4
§4 · The Craft Layer

The discipline we adopted

We adopted the discipline of companies that ship hardware · where a mistake can't be patched Tuesday, so it can't ship at all.

  • Nothing renders unverified. Every surface is eyes-on checked at phone, laptop, and cinema widths first. Proof means a screenshot a human actually looked at, never just a passing status code.

  • Text is unbreakable, zero exceptions. No overlapping text, no clipped words, no one-word-per-line columns, at any width from 320px to a wall-sized display. The one rule with recorded zero leniency.

  • Nothing opens blank. Every input arrives pre-warmed with a real, editable suggestion. Every canvas opens alive. A blank box is a small cruelty, we outlawed it.

  • No dead ends, by law. "I can't" is never a final answer from anything we ship, the Help Imperative, and it's a release gate, not a vibe.

  • Attention is a physical budget. Pull over push, one next-right-thing over forty KPIs, disclosure that unfolds progressively. Focus is spent like money, and we account for it like money.

  • Dark mode is either stunning or absent. A cheap gray night theme is banned outright. (Check ours, the toggle is in the header.)

This is what "Apple-level detail" actually means when you operationalize it: not taste as decoration, but taste as enforcement.

Unbreakable currents. Moats hold their radius even at extreme energy, the same text law above, felt as physics.
No blank field. Born already formed; pre-warm is mandatory. Nothing here opens as a void waiting to be filled.
Attention as budget. Ambient noise quiets itself inside the emblem, focus has a cost, and the system pays it so you don't have to.
No dead ends. Outer containment returns every drifter, nothing here is allowed to just wander off and stop.

live, the same paragraph, every width

No overlapping text, no clipped words, no one-word-per-line columns, the same sentence, reflowing honestly at whatever width you give it, from a phone in a pocket to a wall-sized display.

frame width: 320px

§5
§5 · The Machinery

Value shown, secrets kept

Controlled GenUI: the AI that cannot freelance

Everyone is bolting text models onto interfaces. We built something stricter: the AI never writes interface code. Not a div, not a style, not a script. It emits a validated JSON intent, and the client renders it using only widgets from a pre-audited registry, each one already tested for text integrity, accessibility, and honest state before the model is even allowed to select it.

Why that restriction is the invention: a model that can emit arbitrary interface can emit an interface that lies. A model that can only fill parameters for parts that already passed inspection cannot construct a lie. The model proposes. The registry disposes.

live, pick an ask, watch it assemble


          

client-side only · A.I. Dogfood sample data · zero paid API calls

Deterministic legality, illegal is impossible, not warned

In our flow builder, a step that can't legally run at a given point cannot be placed there. Each step's outputs widen the data context; each candidate's requirements are checked against it (requires ⊆ context). No error dialogs after the fact, the wrong move never appears on the board.

live, add the next step

  • Route the signed contract to the vault
    needs: a signed contract in context, nothing's been signed yet at this point in the flow, so this step is absent, not just disabled.
  • Charge the saved card
    needs: a payment method in context, this flow never captured one, so this step cannot exist here.

The truth machinery, verified / unverified / could-not-find

Every factual claim our systems handle carries one of three classes, and the third · we looked and found nothing · is mandatory. Below every result: the drawer. Nothing is deleted; the noise is labeled and set aside, checkable. This page eats its own law, the drawer at the bottom classifies its own footnoted claims.

VERIFIED: sourced & dated DERIVED: our math, shown COULD-NOT-FIND: the honest nothing
↓ open the full drawer for this page

Provenance at birth

Every record on the spine is born carrying who created it, when, where, under which consent version, with which rights, not added later, born with it. As generative AI floods the world with unattributable content, a data layer where everything arrives pre-receipted stops being hygiene and starts being the product.

Whoacct_a118
When2026-07-22
Wherefilefriend
Consent v.v3
Rightsprivate

Notifications that respect you

We don't interrupt you to feel important. The system prepares; you arrive; it's ready, the doctrine across every surface.

live, pull, not push

a normal day, their way

0

a normal day, our way

your brief is ready when you want it.

§6
§6 · The Ideals, and the features that prove them

Values, with receipts

Values are cheap. Here's ours with the receipts attached, each ideal paired with the shipped mechanism that makes it involuntary.

The honest friend, we'd rather earn a person than trap them

↓ enforced by

Our flagship's paid loop has no subscription to trap you in, pay per document, walk away whole. Where subscriptions exist, cancel-is-one-click / pause-not-punish is codified, release-gated law.

No surprise charges, ever

↓ enforced by

Every paid operation shows its cost before you commit. Renewal warnings are law. The word "surprise" has no billing meaning here.

The open door

↓ enforced by

Browse everything without an account. No card wall, no email ransom for looking. The till gates spending, never curiosity.

Your work is yours

↓ enforced by

Open-format, lossless export is written into our law and built into every canvas that ships. We made leaving easy on purpose, the experience is the lock-in, so the door doesn't have to be.

No dark patterns, as law, not policy

↓ enforced by

Confirm-shaming, fake scarcity, roach motels: banned in the codified law, and release-gated. A dark pattern here fails the build.

§7
§7 · The Marketing We Don't Do, and A.I. Dogfood

The design guides. The experience keeps.

Our growth doctrine fits in one sentence: the design does the guiding, and the experience does the keeping. No funnel mechanics, no manufactured urgency, no exit-intent popups begging you to stay. If the product can't keep you, we deserve to lose you, that's the forcing function, chosen on purpose.

And then there's A.I. Dogfood. Every software company demos with fake data; most let the fake leak, fabricated testimonials, sample records dressed as real ones. We solved it with a law and a mascot: a sample is a picture; fake data in a real slot is a forgery. So we built an entire fictional dogfood company and made it the universal demo identity across the platform, every example document, every showcase flow wears the dogfood brand. No visitor is ever fooled, no real slot ever holds a fake record, and our demos got funnier in the bargain.

the running joke, in one card

est. never
A.I. Dogfood™
our fictional demo company · appears on every sample record, every property, on purpose
§7.5
§7.5 · The Small-Business Proof

A window-cleaning route is our favorite spec sheet

We know a real one, a working window-cleaning company whose owner did what every serious operator eventually does: the software market failed him, so he built his own CRM with the tools he had. He got real things right the enterprise suites never will, a contacts table with fields for spouses' and dogs' names, because he understood twenty years before the industry that rapport is data. He hand-rolled a lead-source field, independently inventing the provenance stamping we wrote into law. The operator was never the problem.

The tooling was. Route order lives in a column of hand-typed integers; the day runs on a printed list with no status, so he re-audits it in his head, all day, asking "did we get everything?" Somewhere in that schema is a column that stores customer passwords. Here's what those same instincts look like with a spine underneath, designed with him, framed as exactly what it is: our next build, not a shipped product.

  • The route orders itself. Geography, live traffic, and per-stop time windows compute the sequence, re-computed as the day moves. The 6–8 AM stop stays pinned; everything else flows around it.

  • The list is alive. Every stop is a card with a real status; done collapses it to a receipt line. A progress bar and end-of-day estimate, computed from his own historical time-on-job, carry the state so his head doesn't have to.

  • A client is one record on one journey · prospect → quoted → booked → routed → done → paid → rebooked, and every stage transition fires the next step itself. The stalled quote taps him on the shoulder.

  • The timesheet builds itself. Consented, visible arrival/departure stamps as the crew works, never covert tracking, and the week's hours land payroll-ready. We kill the Sunday-night hour-reconstruction ritual.

  • And the password column can't exist here. Not "we chose not to": the architecture has no slot for it. Identity lives on the auth rail; a credential in a data table is structurally impossible.

Small business is a central value here, not a segment. The field-service market charges owners like him seventy dollars a month for near-zero-cost software, gating the useful parts. We build the opposite: honest tools at honest prices, and a standing plan we call aggressive kindness, when your slow season comes, your bill should know it.

the glimpse, sample design (not a public live product)

The James CRM glimpse is a private design sample, it is not served on this public site, so we do not embed a frame that would soft-land on the home page. The story above is the honest public face of that intent.

§8
§8 · Where the Spine Goes Next

The floor is live. The interconnect is the point.

What's live is the floor; the interconnect is the point. Coming down the same rail, framed as exactly what they are, plans:

  • Agents that live on your spine. An agent you configure once that remembers your goals, travels with your account across every property, and leaves receipts for everything it does. Not a chatbot per site · your staff, on your record.

  • Messaging as the missing middle. The products talk to your records today; the plan is for them to talk to your people, same provenance, same honesty classes, same no-dark-patterns law applied to the most abused channel in software.

  • The brief, in your own style. A recurring personal brief composed when you arrive, rendered in your own visual identity. We checked the market: no product currently renders a recurring AI brief in the user's own style rather than the company's brand. That gap is scheduled.

  • Research that compounds instead of evaporating. A private knowledge base, documents, findings, receipts, queryable in plain language, with research threads as first-class objects you return to and extend, not disposable chats that forget. Beyond that, gated behind counsel: a research commons where contributors own their seat and benchmarks flow back to them, the anti-data-broker, built consent-first.

  • War rooms. Live, multiplayer intelligence, a team inside one continuously-updated picture of a market instead of forwarding stale PDFs. The dossier stops being a document and becomes a place.

Already wired end-to-end on one spine: intake a lead conversationally → it becomes a record → route the contract for signature → the signed doc chains into the vault → the automation fires → the research crew profiles the next prospect. Six categories of software, zero integrations, one record.

§9
§9 · The Moat

What covering this would cost elsewhere

The categories our live products cover today: e-signature, writing, automation, forms, and competitive intelligence.

The queued bench, conversation automation, artist growth, will widen that list when its machinery is real; we don't count a category until we've shipped it. At the enterprise end of the intelligence category, the incumbents don't publish prices at all, you can't see the number without a sales call.

Now the harder question, what stops anyone from cloning this? Features don't defend themselves anymore. Here's what does:

  1. 1
    The laws are machines. Sixty-nine sections of codified operating law, twelve automated gates that physically block a violating build at the deploy line. A competitor can copy a screen in a weekend. Copying a legal system that compiles is a different sport.
  2. 2
    The spine can't be retrofitted. One account, one wallet, one record store, provenance stamped at birth, day-one architecture. Bolting that onto seventeen separate products after the fact is a rebuild, not a feature.
  3. 3
    The taste is compiled. A month of founder rulings, every naming decision, pricing floor, design law, honesty rule, lives as a versioned, machine-readable corpus every worker builds against. That's not documentation; it's institutional memory with enforcement powers, and it's why the next thousand decisions stay consistent with the last thousand.
  4. 4
    The honesty is structural. Verified/unverified/could-not-find, the audit chains, controlled GenUI. competitors can claim trustworthiness; ours is checkable by strangers. Trust you can verify compounds. Trust you assert doesn't.
§9.5
§9.5 · The Time Receipt, and the Founder

One month.

Here is the number that reframes everything above: the first commit in this repository is dated June 26, 2026. It is now July 26, 2026. Everything built in between, counted:

1,092
commits
30
days elapsed
3,739
tracked files
12,147
lines, one backend
43
registered widgets
23
registered SKUs
13
public properties
69
law sections
12
machine gates

That pace wasn't luck, and it wasn't a team of forty. One founder built an operating system for making decisions before building the products, then directed an agentic workforce against it. "So the AI wrote it all?" is backwards: an agentic workforce with no legal system produces a thousand commits of drift; this one produced a thousand commits of convergence, because every worker built against the same compiled judgment, behind the same gates. That's the founder's actual output, not the keystrokes, the system that makes the keystrokes consistent.

And if the solo part worries you: current Carta-based data shows funded solo founders raise at valuations nearly identical to teams, the real filter is getting funded at all, which is precisely what a page full of checkable receipts is for. The evidence is this page, and the git log stands behind every line of it.

§10.9
§10.9 · The Wave

Every SaaS company owes you this paragraph

Every honest software company owes you this paragraph, and almost none will write it: AI has collapsed the cost of building software, every category is flooding with clones, features stopped being moats. Public-market software has already been repriced on exactly this fear, as one AI-agent startup's CEO put it to Fortune this February: "the software slump is proving that code alone was never a real moat."

We're not different because we ignored the wave. We're different because we built assuming it, on the record. Our own law rules the model a commodity input; the moat lives in what's wrapped around it, the spine, the grammar, the laws, the personalization. Every model upgrade rides along without a tax, not a threat, and the flood of synthetic everything makes our provenance layer more valuable every month.

Forbes carried the same idea from an investor at Quiet Capital this spring, minus the euphemism: building software got fast; trust, data, and habits did not. We spent our month building the things that take years to copy. The wave that's drowning feature factories is our tailwind. That was the design.

§10
§10 · The Valuation. No Bullshit

Pre-revenue. Zero customers. We'll say it first.

Pre-revenue. Zero customers. We'll say it before you can, because what follows only works if you trust it, and every input below is shown.

Applying the four standard pre-revenue methods, with current reference benchmarks (each sourced + dated in the drawer, or flagged honestly where we couldn't pin the source down):

Cost-to-Duplicate (the floor)

  • 8–12 engineers
  • × 12 months, loaded cost
  • replicating 13 shipped properties + backend + widget registry + codified law
$1.5–2.5M

the method's own literature says it undervalues AI-accelerated builds. A floor, labeled a floor.

Berkus Method

  • Sound idea: $350–450K
  • Product quality: $500K (full cap)
  • Execution capability: $300–400K
  • Strategic relationships: $50–100K
  • Rollout underway: $100–150K
$1.3–1.6M

at classic caps; the method's own author sanctions regional/inflation adjustment, landing it near $2.5–3M.

Scorecard Method

  • Product/tech: 150% of typical
  • Opportunity size: 125%
  • Team (velocity vs. solo risk): ≈110%
  • Competition (scored honestly): 70%
  • Channels: 60%
≈ $8.5M

composite ≈ 1.1× anchored on a ~$7.7M pre-seed reference point we could not fully confirm, see D10.

Risk-Factor Summation

  • Technology: +2
  • Stage: +1
  • Exit potential: +1
  • Competition: −1
  • Funding history: −1
≈ $8.2M

net +2 × $250K on the same unconfirmed ~$7.7M anchor.

The honest band: a floor near $2M, a scorecard-anchored center near $8–9M.

~$2M floor~$8–9M center

For calibration, the current median seed round prices companies at $20M post with far less shipped than this · proof that a month of this operation's time compounds like a year of everyone else's. We're not asking you to believe a number; we're showing the arithmetic and the receipts, and letting you do what operators do: check the work.

All benchmarks as of 2026-07-26; valuation data moves, the drawer below carries every source.

The Drawer. This Page, Audited

Every claim, classified

Every footnoted claim above traces here. Nothing was deleted for being inconvenient, the could-not-find entry is included on purpose, because a page that only tells you what it found is lying somewhere. This one doesn't.

D2

Entitlement is resolved server-side, never client-flippable

verified
Basis:
the entitlement endpoint exists and resolves account access on the server, checked directly in the codebase
Method:
grep -n "account/me" app.js
Verified:
2026-07-26
↑ back to §3
D3

No product renders a recurring AI brief in the user's own visual style

could-not-find
What we checked:
the current market for AI daily-briefing / personalized-email products, 2026-07-26
What we found:
brand-consistency tools (keeping a company's own colors/logo steady across generated assets) and house-styled briefings from large platforms, none that render in the recipient's own visual identity
Honesty note:
an honest "we looked and didn't find it": not proof that nothing exists anywhere
↑ back to §8
D5

Solo founders raise at valuations near-identical to teams

verified
Finding:
dilution nearly identical between solo- and multi-founder companies through 2024; valuations nearly identical by Series A, with a mild bias against solo founders specifically at Priced Seed
Accessed:
2026-07-26
↑ back to §9.5
D6

"the software slump is proving that code alone was never a real moat"

verified
Attribution:
quoted CEO of an AI-agent developer-tooling startup, on the public-market SaaS selloff (individual not named on this page by house policy)
↑ back to §10.9
D7

AI compresses build time, not the time for things to actually happen

verified
Attribution:
an investor at Quiet Capital, on defensibility in the AI era (individual not named on this page by house policy; paraphrased rather than quoted at length)
↑ back to §10.9
D9

Scale receipts: commits, files, widgets, SKUs, gates, law sections

verified
First → latest commit:
2026-06-26 → 2026-07-26
Commits:
1,092
·
Method:
git rev-list --count HEAD
Tracked files:
3,739
·
Method:
git ls-files | wc -l
Backend size:
12,147 lines
·
Method:
wc -l app.js
Registered widgets:
43
·
Method:
counted entries in the WIDGETS registry array
Registered SKUs:
23
·
Method:
counted entries in the STRIPE_PRICES map
Law sections:
69
·
Method:
grep -c "^## [IVXL]" CLAUDE.md
Machine gates:
12
·
Method:
counted gate-/guard- scripts in the scripts directory
Accessed:
2026-07-26 re-run live against this repository while building this page
↑ back to §9.5
D10

Pre-seed pre-money reference point: ~$7.7M

could-not-find
Attempted source:
PitchBook–NVCA Q3 2025 Venture Monitor, p.10, "Median VC pre-money valuation ($M) by series"
Note:
We downloaded and read the actual PDF. The string "$7.7" is genuinely in that chart's cluster of stacked value labels for six series (Pre-seed/Seed/A/B/C/D+). but the chart's own Pre-seed line sits within a pixel of $0 on a $0–1,000 axis at its 2025 endpoint, overlapping the Seed dot with no distinguishable number of its own, so we could not confirm $7.7 is specifically the Pre-seed value rather than another series or year in that cluster. Carta's own State of Pre-Seed report, the more likely original source for a quarterly pre-seed figure, returned a 403 on direct fetch and could not be corroborated via secondary coverage either. Kept as an honest reference point, not a sourced fact.
Accessed:
2026-07-26
↑ back to §10
D12

Cost-to-duplicate estimate: $1.5–2.5M

derived
Method:
standard cost-to-duplicate heuristic (replacement engineering effort × loaded cost). a widely-taught early-stage valuation approach, not a single cited source
Inputs shown:
8–12 engineers × 12 months, shown alongside the figure in §10
Label:
explicitly presented as a floor, not a center estimate
↑ back to §10