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.

How far has each idea actually been proven?

We advance claims through five evidence states rather than using a vague percentage-complete score.

Four connected product families.

42For people
75For work
6Build with Widerloom
19Shared systems

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
EvidenceIdentityRecoveryAgentsPublishingObservabilityPrivacyPortability

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
ProductWorking priceQuantity meansMonthly quantityGross revenueContribution
$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.

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.

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.

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.

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.

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.

142 of 142 shownAll primitivesAll archetypes

Practical tools for decisions, resilience, creativity, and everyday life.

Small enough to be useful immediately, designed to become more valuable together over time.

In development

Studio Companion

A durable companion for creative practice: preserve process, materials, context, experiments, provenance, and the story around work without turning making into administration.

Creative practice · customer-owned record
Prototype

Cooking Companion

Context-aware cooking help that adapts recipes and plans around ingredients, constraints, preferences, substitutions, timing, and what is actually practical right now.

Compiled product prototype
Prototype

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.

Compiled product prototype
Prototype

Scheduling Tool

A configurable scheduling product for real-world service workflows, designed around clear constraints, handoffs, exceptions, and portable operational data.

Initial domain: HVAC scheduling

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.

Prototype

Professional Document Preparation

Evidence-aware document workflows that gather inputs, preserve source context, structure drafts, expose missing information, and create reviewable deliverables.

Compiled product prototype
Prototype

Small Practice Financial Reporting

Clear reporting for small practices: transform operational financial data into understandable views, explanations, exceptions, and decision-ready outputs.

Compiled business product prototype
In development

Experience Intelligence

Connect signals across customer experience, behavior, outcomes, friction, evidence, and feedback so teams can see what is happening and what deserves attention.

Product intelligence
Exploring

Whole-Life Economics

Tools for seeing money, time, resilience, obligations, optionality, and future freedom as an interconnected system rather than isolated financial metrics.

Emerging product direction

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.

Prototype

Website Foundry

From brand and intent to semantic design system, distinctive live directions, conversational refinement, governed publishing, hosting, portability, and ongoing evolution.

Contract and prototype stage
In development

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.

Architecture built · device/store proof still in progress
Exploring

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.

Future product · architecture kept open

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.

In development

Control Room

An operator view across launches, revenue, risk, CI, observability, recovery, evidence, maturity, failures, implications, and next actions.

Internal-first operator product
In development

Connections + Intelligence Vault

A purpose-bound, provenance-aware system for connecting information, understanding it, remembering appropriately, and acting only within explicit authority.

Connect · Understand · Remember · Act
Prototype

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.

Exploratory capability
Prototype

Optionality Engine

Maps reusable primitives, audiences, evidence, obligations, dependencies, economics, and future paths to help preserve valuable choices as a system evolves.

Experimental capability
In development

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.

Shared trust primitive
In development

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.

Internal-first reliability system
In development

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.

Trustworthy agent infrastructure
In development

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.

Recovery and portability system
In development

Compliance + Trust Registry

A living crosswalk of controls, evidence, assurance requirements, accessibility, performance, privacy, security, and external review readiness.

In development

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.

Shared product substrate

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.

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

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.

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.