A LIVE DEMO · MALLEABLE SOFTWARE, ILLUSTRATED ON EMAIL
YOUR INBOX, RESHAPED ON DEMAND

Your inbox is
finished until
you reshape it.

Same inbox for the CEO, the founder, the investor, the operator — anyone, really. Built for nobody in particular. Watch it become a kanban, a pipeline, a trip, a sheet.

See the demo
Malleable software, illustrated on email. The same shape-shift works on any product. Learn More
Inbox 1,247 unread
9:41
Marc Chen Re: Series A — happy to share our deck 9:42
Air Canada Your flight to Lisbon, May 19 — boarding pass 9:30
Stripe Receipt for $89.50 — Marriott Lisbon 8:55
Sarah K. Re: intro to Mei — when are you free? 8:14
QuickBooks Invoice #2087 paid · $1,200 received Yest
Notion Workspace digest — 12 mentions you missed Yest
reshape
Needs reply
47 threads
Sort it
$6.4M
Pipeline · 30 investor threads
· · · · · · · · · · · ·
FIRST TOUCH → CLOSE 17 stale
∿ ∿ ∿
Open
Lisbon · Tue
Stitch trip
View
𝍖
Receipts
82 vendors, YTD
Export

One inbox. Many shapes
it should already be.

It doesn't matter who you are. CEO, founder, investor, operator, freelancer, parent — anyone with an inbox already lives inside these four pains. The structure is sitting in the messages. The client just won't render it.

→ Kanban for replies
Ask: "turn my inbox into a board — Needs reply / Waiting on them / Done." Email has no concept of state. A thread is just a sequential log. The status of every commitment lives entirely in your head, and your head is a leaky cache. New mail pushes old promises out of view. Dropped balls become invisible by design.
STRUCTURAL PAIN · EMAIL HAS NO STATE
→ Deals pipeline
Ask: "show my investor threads as a pipeline." Columns become stages — First touch, Pitched, In diligence, Soft commit, Closed. Amounts, last-touch dates, next steps extract themselves. The truth was always in email; the CRM was the copy nobody updates. No view ever told you "Marc hasn't heard from you in 17 days." Now it does.
STRUCTURAL PAIN · DOUBLE BOOKKEEPING
→ Trip stitcher
Ask: "I'm flying to Lisbon Tuesday, show me my trip." Flight, hotel, conference pass, dinner reservations, Uber receipts — eight to fifteen emails from six vendors, weeks apart — stitched into one day-by-day with map and timeline. The trip is the unit that matters. Email is filed by sender. The grouping you actually need doesn't exist in the data structure.
STRUCTURAL PAIN · WRONG UNIT OF GROUPING
→ Receipts as rows
Ask: "pull every receipt and invoice this year into a sheet." Order confirmations, SaaS invoices, Stripe receipts parsed into rows — vendor, amount, category, date, currency. Export-ready for QuickBooks. The structured data was sitting inside unstructured prose, in 200 formats, from 80 senders. Email just refuses to admit it's data. So you, the human, become the OCR pipeline.
STRUCTURAL PAIN · DATA HIDING AS PROSE

Your inbox isn't broken.
It's a task manager wearing a list's costume.

The inbox isn't an inbox anymore.
It's whatever you need today.

The same shape-shift works on any product. Below, it's running on a conference app — pick a person, ask the wall to break. Ask it to become a radar of fit, a deal pipeline, a booth heatmap, a hiring board. The interface itself changes. Now imagine that same chat sitting next to your inbox — "turn this into a kanban of replies," "show my investor threads as a pipeline," "stitch every receipt this year into a sheet." Same data. New application. This is what malleable software actually does.

Two audiences. One promise:
your software bends.

Malleable software isn't a feature. It's a fundamentally different way of building products. Email is the cleanest example — the structure is already there in the messages, the client just won't render it — but the same shape applies to any app where users keep escaping into Notion, Sheets, or another tab. Here's what it delivers.

→ FOR THE SOFTWARE COMPANY
Your power users stop leaving for spreadsheets.
Today, your top 5% rebuild your product in Notion, Sheets, and Zapier — because your app can't bend. Email clients lose them to Superhuman snippets, CRMs, trip apps, and accounting exports. You ship the layer that lets them reshape your product instead.
  • Higher retention. The user who shapes their own view doesn't churn.
  • Premium pricing tiers. Power users pay 3-10× for the malleable layer.
  • Onboarding stops being a tax. Users build their version on day one.
  • A moat that compounds. User-built shapes get shared and forked. Competitors can't copy that.
→ FOR YOUR END USER
Stop waiting for someone else to build it.
They know their job. You don't. Now they reshape your product from the inside — no second tool, no copy-paste, no forwarding everything to TripIt or HubSpot.
  • Filter: "Show me only threads I owe a reply to" — the inbox becomes a kanban.
  • Reshape: "Turn my investor threads into a pipeline" — the app grows CRM columns.
  • Build new: "Stitch my Lisbon trip from these emails" — a whole new section appears.
  • Save it. Share it. Your view becomes your team's. No second spreadsheet.

Software should bend to the human.
Not the other way around.

The strongest demo isn't "email looks different." It's "you forget you're using an email client at all." Your inbox already contains structured workflows and structured data — the kanban states, the pipeline stages, the trip, the spreadsheet of receipts — it just presents itself as flat prose. The structure was always there. The client was just refusing to render it.

The best apps of the next decade will not be the ones with the most features. They will be the ones users can reshape into the tool they actually needed. The roadmap dies. The user becomes the developer. The product becomes a substrate.

The question isn't whether this is coming. It's whether it ships inside your product, or outside it.