Decision Packet
A human-reviewed, evidence-aware brief for consequential decisions: what the evidence supports, what remains uncertain, credible alternatives, counter-cases, and the cheapest useful next proof.
What we're making
A living map of what Widerloom is becoming.
Products, shared capabilities, and experiments shown by their actual state. Explore visually first; open the detail only when you want it.
Loading catalog projection…
Founding releaseIn developmentPrototypeExploring
142active products + capabilities
1release
17building
58prototype
66exploring
The shape of the portfolio, not a marketing funnel. Most of Widerloom is intentionally still earning evidence.
Evidence maturity
How far has each idea actually been proven?
We advance claims through five evidence states rather than using a vague percentage-complete score.
Portfolio shape
Four connected product families.
42For people
75For work
6Build with Widerloom
19Shared systems
How the system compounds
The products are connected, not isolated.
Shared capabilities sit at the center. Product families inherit evidence, governance, recovery, publishing, privacy, and intelligence rather than rebuilding them from scratch.
For people42
For work75
Build with Widerloom6
Shared systems19
Shared substrate
GTM + unit economics
Model revenue, cost, margin, and capacity together.
Prices remain working hypotheses. This layer makes the assumptions around acquisition, discounting, payment costs, refunds, delivery effort, support, and recurring churn visible so the product mix can be pressure-tested economically.
$0gross monthly revenue
$0net monthly revenue
$0monthly contribution
Not modeledcontribution margin
$0annualized gross run-rate
0%modeled service capacity
| Product | Working price | Quantity means | Monthly quantity | Gross revenue | Contribution |
|---|
$0acquisition spend
$0fees + refunds + delivery + support
Not modeledmodeled recurring base after 12 months without replacement
Planning model only. It is intentionally assumption-driven and does not claim observed unit economics. Taxes, fixed overhead, payroll allocation, tax effects, cohort-specific retention, channel attribution, financing, working capital, seasonality, and product-specific cost curves remain outside this v1 model.
Commercial intelligence
What has to be true for this portfolio to reach the revenue target?
Reverse-plan the path from outcome to demand, funnel, capacity, capital, retention, and proof. The model keeps hypotheses visibly separate from observed evidence.
Checking observed evidence…
Observed aggregate commerce evidence may inform the model, but never silently overwrites scenario assumptions.
$0modeled portfolio revenue
$0 gapdistance to target
0customer-equivalents required
0qualified leads required
$0modeled acquisition spend
$0gross contribution after CAC
Paths to the target
Design the mix instead of betting on one product.
Revenue weights normalize automatically. Customer burden incorporates catalog price hypotheses, time horizon, and recurring-product churn.
| Product | Mix weight % | Customers | Modeled revenue | Target share |
|---|
Constraint forecast
See what breaks before the spreadsheet says “success.”
Demand, fulfillment capacity, acquisition budget, contribution economics, evidence quality, and release readiness are checked independently.
Full funnel
Work backward from customers to attention.
Revenue per relationship
Let the portfolio compound around a customer.
Attach rate estimates the share of customer relationships expected to use each product during the modeled horizon.
$0expected portfolio value / relationship
0relationships to reach target
Path to the target
Make the climb legible.
Milestones show how the current portfolio mix translates into increasing commercial scale. They are trajectory markers, not promises.
Observed vs hypothesized
Evidence earns the right to replace assumptions.
Reverse-demand planner
If one product carried the target, how much demand would it need?
This is a stress test, not a product recommendation.
| Product | Revenue / customer | Customers for target | Demand unit |
|---|
Planning assumptions only.
Truth boundary: prices, conversion, CAC, margin, churn, attach rates, funnel assumptions, capacity and mix remain hypotheses until replaced by observed evidence. Observed aggregate metrics are shown separately. The surface informs human commercial decisions and may emit next-proof signals to the harness, but it does not authorize spend, launch, pricing changes, or product prioritization by itself.
First 20 finish runway
Finish the products that make the next products easier.
Four waves turn the catalog into a compounding sequence: prove demand and revenue, productize assurance expertise, expand repeatable work products, then open the personal-life lane.
Finish readiness
Source-complete is not the same as proven in the world.
The first 20 are tracked across source, staging, customer, commerce, external review, and observed-use evidence. This keeps “done” honest while still showing how much has actually been completed.
Living visual vocabulary
The products are teaching Widerloom how to explain complexity better.
Every first-20 product contributes semantic visual primitives. Reused patterns graduate toward the shared vocabulary; product-specific patterns stay experimental until they earn broader usefulness and comprehension evidence.
Experience archetypes
Different problems need different product shapes.
The catalog is not one template repeated 142 times. Products compile into decision systems, monitors, continuity systems, assurance systems, intelligence products, workflow products, platform products, personal tools, and operating products based on the work they need to help people do.
Select an archetype to filter the product universe. Archetype describes experience shape, not product quality, rank, or readiness.
Portfolio terrain
Every identified product, plotted by evidence instead of hype.
This is the portfolio as a landscape. Move left to right as evidence strengthens. Move vertically across the four product families. Larger circles use more shared Widerloom capabilities. Select any node to inspect its role and next proof.
For people
Practical tools for decisions, resilience, creativity, and everyday life.
Small enough to be useful immediately, designed to become more valuable together over time.
Studio Companion
A durable companion for creative practice: preserve process, materials, context, experiments, provenance, and the story around work without turning making into administration.
Cooking Companion
Context-aware cooking help that adapts recipes and plans around ingredients, constraints, preferences, substitutions, timing, and what is actually practical right now.
People Context Assistant
A privacy-respecting way to remember the context that helps relationships: commitments, shared history, useful details, and follow-through, with explicit boundaries around sensitive information.
Scheduling Tool
A configurable scheduling product for real-world service workflows, designed around clear constraints, handoffs, exceptions, and portable operational data.
For work
Tools that turn messy operating work into clear, durable capability.
Designed for small organizations, professional teams, agencies, and the people who need systems to fit the work rather than the reverse.
Professional Document Preparation
Evidence-aware document workflows that gather inputs, preserve source context, structure drafts, expose missing information, and create reviewable deliverables.
Small Practice Financial Reporting
Clear reporting for small practices: transform operational financial data into understandable views, explanations, exceptions, and decision-ready outputs.
Opportunity Intelligence
Continuously find and organize RFPs, RFIs, RFQs, grants, procurement notices, partnerships, agency overflow, inbound opportunities, and public signals. Ingest the source, preserve its requested structure, extract requirements and deadlines, research context, assess fit and risk, and prepare response work.
Experience Intelligence
Connect signals across customer experience, behavior, outcomes, friction, evidence, and feedback so teams can see what is happening and what deserves attention.
Whole-Life Economics
Tools for seeing money, time, resilience, obligations, optionality, and future freedom as an interconnected system rather than isolated financial metrics.
Build with Widerloom
Products and websites built to belong to the people who commission them.
Widerloom is building a secure product foundry for organizations and agencies that need custom software without creating unnecessary lock-in.
Secure Product Foundry
Custom products that integrate with existing systems instead of demanding rip-and-replace. API-first interoperability, explicit ownership, tenant isolation, observability, portability, recovery, and clean handoff are part of the product, not afterthoughts.
Website Foundry
From brand and intent to semantic design system, distinctive live directions, conversational refinement, governed publishing, hosting, portability, and ongoing evolution.
Native App Forge
A reusable path from product model to native surfaces, including capability and sync compilation, release metadata, provenance, software bills of materials, portability, and possession-ready handoff packages.
Private Collective Giving
A privacy-preserving way for many people to fund something together while the public sees the aggregate rather than donor identities or individual amounts, with strong internal auditability.
The systems underneath
Some of our most interesting products begin as infrastructure we need ourselves.
These are internal-first capabilities. Where they become independently useful and earn enough evidence, they may become products of their own.
Control Room
An operator view across launches, revenue, risk, CI, observability, recovery, evidence, maturity, failures, implications, and next actions.
Connections + Intelligence Vault
A purpose-bound, provenance-aware system for connecting information, understanding it, remembering appropriately, and acting only within explicit authority.
Simulation Lab
Stress-test products and operations against demand, support, provider failure, privacy, cost, reputation, recovery, and other scenarios before reality does it for us.
Optionality Engine
Maps reusable primitives, audiences, evidence, obligations, dependencies, economics, and future paths to help preserve valuable choices as a system evolves.
Evidence Engine
Keep claims connected to evidence, provenance, uncertainty, freshness, and review state so systems can distinguish what exists from what has actually been proven.
Change Assurance + Failure Intelligence
Understand what a change could affect, verify what actually happened, learn from failures, and make safer changes without treating every incident as an isolated event.
Governed Agent Runtime
Bound AI agents by identity, authority, policy, evidence, verification, receipts, and human control so automation can become more capable without becoming opaque.
Recovery Engine
Backups are not recovery. This system is about reconstructability, independent copies, restore proof, provider failure, continuity, and giving owners something they can actually take with them.
Compliance + Trust Registry
A living crosswalk of controls, evidence, assurance requirements, accessibility, performance, privacy, security, and external review readiness.
Product Factory + Publisher
A shared system for turning researched ideas into bounded experiments, reusable Product Units, release-ready packages, governed launches, customer entitlements, and evidence-driven evolution.
Compounding capability
Build a primitive once. Let many products inherit it.
The strongest parts of Widerloom should compound. This view shows which shared capabilities recur across the portfolio. Select one to see the products it strengthens.
Why reuse matters
Identity, evidence, recovery, privacy, observability, publishing, and governed action should not be reinvented product by product. Reuse lowers failure risk while making each new product faster to build and easier to improve.
These are architectural relationships, not claims that every primitive is production-proven.
Product × primitive matrix
See what each product uses, and how ready those shared pieces are.
Each dot means the product materially depends on that primitive. Dot state reflects the primitive's current platform readiness, so the same view exposes both reuse and build debt.
Ready to reuseIn progressNeeds build or proofNot used
Primitive readiness
What is reusable now, and what still has to be built.
This is the build map behind the portfolio. It separates a primitive existing in the architecture from being reliable, governed, and proven enough for repeated customer use.
Why show unfinished work?
Because the frontier is part of the story.
We would rather show what we are trying, what state it is actually in, and what still has to be proven than make a small company look artificially finished. This catalog will change as products earn evidence, combine, evolve, pause, or disappear.
This staging catalog shows every currently identified Widerloom product direction. Inclusion means identified, not launched, deployed, validated, committed to the roadmap, or authorized for sale.