Maximas Foundry

Where we build and own AI-native businesses ourselves

The Foundry is the second engine inside MaximasOne. We identify the opportunity, validate it, build it, and own it — the same execution we bring to founder partnerships, carried at our own risk.

One company, two engines

How MaximasOne is organized

MaximasOne Partner

We build with founders.

You bring the domain insight and customer access. We bring product, AI engineering, and operational execution as an embedded co-founder, with part of our compensation tied to the outcome.

Maximas Foundry

We build for ourselves.

We identify the opportunity, validate it, build it, and own it. Same process, same standards — with our own capital, time, and reputation on the line.

Alongside both, Workflow Consulting brings the same AI capability to established companies that want their existing teams to do more of the work they care about. See Workflow Consulting.

The selection thesis

These aren't four industries. They're one filter.

Inventory, CRM, insurance operations, and niche commerce look unrelated until you see what they have in common. We build in the Foundry only when an opportunity meets all four criteria.

Painful manual workflows

High-touch, repetitive knowledge work that people do because the software never did it for them.

Fragmented legacy software

Disconnected systems and portals where the same information is entered more than once.

Proprietary domain data

Data that is hard to access from the outside and valuable to whoever can organize it.

AI changes the unit economics

A clear leverage point where machine intelligence materially changes the cost of doing the work.

What we're building

The thesis in practice

Each build starts from a specific operating problem. Details are kept at teaser level while partners and pilots are under confidentiality, and we publish results only once they're real.

In development

Inventory Management Software & Mobile App

Inventory & logistics

Problem: Stock lives in spreadsheets and legacy desktop systems, so counts are only accurate at the desk — never on the floor, in the warehouse, or on the road.
Build: A web dashboard paired with a companion mobile app, with intelligent reconciliation of counts, movements, and reorder signals across locations.
What we're targeting: Removing duplicate manual entry and keeping one accurate stock position across every location.

Full reveal coming soon

Live

Custom CRM

Sales & operations

Problem: Generic CRMs force a team to work the way the software was designed, so the record of the relationship ends up incomplete and the pipeline stops being trusted.
Build: A purpose-built CRM shaped around how the team actually sells — contacts, pipelines, and follow-ups, with the admin work drafted and prompted rather than typed.
What we're targeting: Less time spent maintaining the system, more time spent in front of customers.

Live now

Launching

InsurTech SaaS for Operations Management

InsurTech

Problem: Insurance operations run across disconnected carrier portals, inboxes, and documents, so the same information is re-keyed repeatedly and nothing gives a single view of the work in flight.
Build: An AI-native operations platform that connects those systems, reads and routes incoming documents, and puts every task and status in one place.
What we're targeting: Cutting redundant multi-portal entry and giving operations leaders visibility over the whole workload.

Launching soon

Validation

Trading Card E-Commerce Store

E-commerce

Problem: Listing, grading context, and pricing for card inventory is slow, manual, and spread across marketplaces that were never designed for the category.
Build: A storefront concept where listings, imagery, and pricing context are generated from the inventory itself rather than typed one card at a time.
What we're targeting: Testing whether the listing workload can be reduced enough to change the economics for sellers.

Concept being validated

More Foundry builds are in the pipeline. Details are shared as each product is ready for public reveal.

How to read the stages

What each label means

Validation

The idea is being tested against real customers before scope is committed.

In development

Design and engineering are running in cycles toward a working product.

Launching

The product is going out to its first users — pilots and early customers are being brought onboard.

Live

The product is launched and in active use, with ongoing iteration and support.

Want this execution behind your idea?

The same team and the same process are available through a co-founder partnership.

Apply to work with us