PLM + PPM · AI-native

The Product OS for modern manufacturers.

Your BOMs, costs, suppliers, orders, lifecycle and launch programs — finally on one source of truth, with an AI that actually knows your data.

Request a walkthrough See what's inside

Ask Iris Order Status · Cardinal Cycles

Which Cardinal Cycles lines are late, and what's holding them?

Two lines on PI-T36420 are past the date we promised.

SKU	Qty	Supply	Promised	State
CS4-RDG-P02	120	VPO-T95210 Sunrise Machinery	24 Sep	3 days late
CS-2047-165	40	TW warehouse 86 on hand	—	Ships this week

The other nine lines are on time. Want me to draft the note to Cardinal?

SourcesPI-T36420VPO-T95210Inventory · TW

Illustration with sample dataAnswers cite the records they came from

The problem

The product lifecycle runs on spreadsheets and hope.

Growing product companies run the whole thing on scattered spreadsheets, ERP exports and email. The BOM is in one file, costs in another, the launch plan somewhere else, supplier status in an inbox. Nothing connects, nothing is current — so products slip, margins leak, and every review turns into an archaeology project. You have outgrown spreadsheets, but you cannot justify a 12-month enterprise-PLM rollout.

See the whole product lifecycle.Trust every number.Move faster than your spreadsheets ever let you.

Why ikkando

One system. Grounded data. AI you can trust.

Not a heavyweight PLM. Not a generic project tool. The one platform built for how products actually get made and brought to market.

One system for the whole lifecycle

PLM and PPM, unified. Other tools give you a BOM or a project plan. ikkando connects them — so the program launching next season is wired to the cost and supplier reality beneath it. No reconciliation tax.

Grounded in your real data

ikkando sits on top of your ERP as the system of record and curates it into one governed source of truth. Every number traces to source — not a spreadsheet someone forgot to update.

An AI that won't make things up

Meet Iris. She answers questions and drafts the busywork from your real, curated records — and refuses to guess. Human-in-the-loop and output-validated: the hardest thing to get right in enterprise AI, built in from day one.

Live in weeks. Better every week.

Modern and ERP-connected: stood up in weeks, not a multi-quarter IT program, and run by your own team. Then it keeps moving — a What's New roster lands inside the product every week, in your team's words, with what they can now do.

What's inside

Everything that moves a product to market — grouped by the job, not by the data.

The navigation reads like the company: what we make, what we plan, what we owe customers, what changed, what sold, what failed. Every module has the same three shapes, so the tenth page is as familiar as the first.

Product what we make

Portfolio & Lifecycle TrackerEvery model, and the stage each one is in across model years — the line plan.
Programs & ProjectsThe work of bringing a model year to market, ranked by what needs attention.
SKUs, BOMs & BOM itemsEvery sellable SKU, what it is actually made of, the engineering assemblies behind it, and the component catalogue underneath.

Supply Chain what we plan

Demand Plan & Supply PlanHow many you intend to sell next model year, family by family — and what to order to meet it.
Inventory & In-transit coverageWhat you hold by SKU and distribution centre, and whether what is on the water fills a real hole.
Vendor CenterThe shared surface with the people who build for you: open orders, the dates they committed to, the plan you want them building toward.

Order Management what we owe customers

Order intakeA customer PO arrives, gets read, and becomes an order in your ERP — matched to the customer and to your SKUs.
ShipmentsThe shipping team's own board: promised-date cards, the containers built from them, the packing lists, the steps ticked as they happen.
Order Status & Order MetricsWhere every order is right now — and on-time delivery, order value and invoicing as three figures first.
Your customer's pageA page a customer signs in to: their orders, their answers, their forecasts, nothing else.

Issues & ECOs what changed

IssuesProblems, findings and risks — recorded, owned and closed, linked to the model, SKU or part they concern.
ECOsEvery deliberate change to a product and who agreed to it. An ECO takes effect on the date it says.

Sales what sold

Pipeline & PricingOEM opportunities by stage, and the negotiated price lists behind them — per customer, per model year, per SKU.
TargetsThe operating plan's sales targets, by channel and category.

QC what failed, and why

Quality PatternsField failures grouped by component and failure mode, so a recurring problem stops looking like isolated tickets.
Standards & Spec analysisThe specifications products are held to — and a place to drop a spec document and have it read, structured and compared.

Iris on every page

Ask, in the palette or out loud⌘K for a question, ⌥Space for a voice call. She knows which page and filters you are on, so "these orders" means these orders.
Multi-view and NotesUp to four live pages side by side, and a notebook that understands the same @-references as every comment box.
Bring your own assistantPoint Claude or any assistant at ikkando's connector and ask for your work without opening the app.

A listBrowse with filter chips. Filters live in the URL, so a filtered view is a link you can send.

A pageOne thing in full — an order, a BOM, an ECO — with its history and its conversation.

A peekClick any id and it opens beside you, so you can look without losing your place.

Iris

Not a chatbot bolted on. A colleague who has read everything.

Iris answers from your curated records — orders, BOMs, plans, changes, the rules your team has agreed — and shows the sources. When the answer is not in the data, she says so instead of inventing one.

The rule she works by: every answer cites the records it came from; every action she takes waits for the person whose job it is to say yes.

In the app⌘K · ⌥SpaceAsk from any page. She is told the route, the record and the filters, and answers in place with next moves as buttons.
On your phoneOn a phone, ikkando is Iris: one big box, the ikkando mark beneath it, and the screen becomes her answer.
In your meetinginvited and namedKeeps the transcript, speaks only when addressed or when something contradicts a rule, and files the work you decided on.
In chat and emailin her own nameA mention, an assignment or a sign-off waiting on you reaches you in chat within a minute; the morning email carries the week.
On any issue@irisMention her in a comment and she picks it up and replies there — the conversation stays on the record.
On paper you drop inDrop a customer PO and it reads itself; drop a BOM and it revises the one you already have; drop a spec and it is structured and compared.

How it works

Your ERP still owns the transactions. ikkando owns the intent that drives them.

Nothing to migrate and nothing to re-key. ikkando mirrors your ERP, curates it into one governed picture, and writes back only what it authored — through the person who approves it.

Your ERP

NetSuite today. It keeps the transactions: items, sales orders, purchase orders, invoices, receipts.

The system of record stays the system of record.

⇄⇅mirrored every hour · authored answers written back through an approval

ikkando

Holds the intent: BOMs and changes, the demand plan, promised dates, shipping answers, the rules — and the shared picture the whole team works from.

One definition of every number, used by every surface and by Iris.

⇄⇅asks, answers, decides — in the app, in chat, on the phone

Your team

Product, supply chain, the order desk, QC, sales — with Iris beside them. And a page your customers and vendors sign in to.

Your existing people run it. No integrator army.

Grounded, not generatedDerived numbers — cost, margin, coverage, on-time — are computed once in a metric layer. Iris reads the same definition your screens do.

Governed by your rulesWhat needs an ECO, who signs, what a status means: written down once, enforced by the app, and quoted by Iris when someone asks.

Yours, not a forkOne product serves every customer. Your rules, labels, routing and sign-offs are configuration — so the platform keeps improving under you.

Built around how your people actually work

Big platforms lose to spreadsheets because they cannot bend. ikkando bends.

Every manufacturer runs on a process that is partly its own. Rigid software fights it, and people quietly go back to Excel. ikkando encodes the process as it actually is — and then changes with the team, week after week.

Ask Iris for a change and it becomes a ticket the developers work. What ships is listed inside the product in plain language, so nobody has to read a release note to find out what they can now do.

14 Sep
A page your customer signs in toA customer account can sign in to see its own orders, send its POs and write to the team — on one page that shows nothing else.
7 Sep
ikkando on your phoneOn a phone, ikkando is Iris: one big box in big type, the ikkando mark beneath it — Press to Ask Iris — and the screen becomes her answer.
7 Sep
Iris joins your meetingName the meeting and the line stays open: she keeps the transcript, speaks only when addressed, and files the work you decide on.
7 Sep
An ECO takes effect when it saysA change with an effective date, a production order or a condition waits at Approved after its last sign-off, and applies when that moment comes.
31 Aug
Drop a customer PO and it reads itselfPut a customer PO on the intake page and it is read, matched to the customer and SKUs, and staged as a draft.
24 Aug
Packing instructions, generatedOn a shipment page ikkando drafts each vendor's packing list, from two years of real packing history.

From ikkando's own What's New — four weekly rosters, 32 things the team can now do.

Why not the alternatives

Outgrown spreadsheets. Not ready for a 12-month PLM.

Spreadsheets & email

Nothing connects

Free and familiar — and exactly the problem. Every file is a silo, nothing is current, and the truth lives in someone's head.

Enterprise PLM

Too heavy

Built for the Fortune 500 — and priced, staffed and timed like it. A 12–18 month, IT-led implementation you cannot justify.

Generic project tools

No product context

No BOM, no cost, no lifecycle, no supply. A shared calendar with no idea what you actually make. A to-do list, not a Product OS.

ikkando is built for where you actually are.

See ikkando on your own data.

A short walkthrough against your real BOMs, orders and lifecycle — not a generic demo.

Request a walkthrough

or write to info@ikkando.app