AI-native agentic layer for manufacturing SMEs
The agentic layer
that runs itself.
Your ERP records what happened. Your team still does the work — in spreadsheets, email and WhatsApp. Kyros puts agents in that gap.
An illustrative activity log showing Kyros agents moving a purchase through the procure-to-pay cycle: raising a requisition from an MRP run, comparing vendor quotes, issuing a purchase order, routing approval to a person, recording goods receipt, flagging defects at inspection for a person to decide, putting stock away under FIFO, and releasing payment after a three-way match.
Illustrative. Not a product recording.
The problem
The ERP records. Someone still does the work.
3 systems
to place one order
The ERP, a spreadsheet, and a WhatsApp thread. None of them agree.
18 months
to implement the last one
Not a timeline a 60-person manufacturer can absorb twice.
2x volume
means 2x the ops team
Growth costs headcount, because the software never took any work.
From our founder and operator interviews, and the pilot we run today.
Every one of these is a person doing work a system should have done.
The MVP scope
Eight stages from “we need it” to “it’s paid for.”
The goal is the whole manufacturing supply chain. We start where the pain is densest. Pick a stage.
Sourcing & vendor selection
Who to buy from. RFQ, comparison, negotiation, selection.
How it works today
Large firms have an approved vendor list and a scoring model. SMEs have phone calls, WhatsApp and relationships, because the volume never justified anything else. Quotes arrive in four formats and get compared in someone's head.
What Kyros does
Issues the RFQ, chases responses across email and WhatsApp, normalises what comes back into one table, ranks on price, lead time, quality history and terms. Negotiation stays with the buyer.
Worth saying — The least structured step in the cycle. The agent removes the chasing, not the relationship.
We are building this loop first. It is high-frequency, completely unstructured, and the one step where ERPs capture nothing — they record the PO, never the sourcing that produced it. No incumbent is attempting it, and there is no existing workflow to disrupt.
Five stages the agents own. Two they assist. One they never touch.
- Now
The sourcing agent
RFQ, follow-up, and ranked quote comparison. In a live pilot.
- Next
The rest of procure-to-pay
Seven more stages, as one coordinated multi-agent system.
- Then
The wider supply chain
Production, planning and finance operations.
How it works
A layer, not a migration.
Kyros runs on top of what you already have. Reads from it, writes back to it. Nothing to rip out.
- No migration
- Deploys against your existing stack.
- Not RPA
- Reads documents instead of replaying clicks.
- ~2 months
- Target time to production, not 18.
Operators
Approvals and exceptions
Kyros agents
Read documents. Reason. Execute.
Your system of record
SAP · Oracle · Tally · spreadsheets
Where this goes
Procure-to-pay is the beachhead, not the ceiling.
Operations
- Invoice generation
- 3-way matching
- Goods receipt
- Carrier assignment
Planning
- Safety stock
- Reorder points
- Demand forecasting
- Production scheduling
Finance
- GL reconciliation
- AP / AR
- Landed cost
We are not automating clicks. We are automating decisions and their paperwork.
Positioning
Not a legacy ERP. Not RPA.
| Dimension | Legacy ERP | RPA bots | Kyros |
|---|---|---|---|
| How it works | Records what people enter | Replays recorded clicks | Reads, reasons, executes |
| On an exception | Escalates silently | Breaks, someone rebuilds it | Resolves it, or names the mismatch |
| Time to value | 12–18 months | Weeks per workflow | ~2 months, as a target |
| To handle 2x volume | Add headcount | Add bots and maintenance | Add volume |
Our time-to-value is the target we build against. We are pre-launch.
Market & model
A market mid-shift.
$1.8B
Indian ERP market
Shifting to cloud, AI-driven SME systems. Our own research.
~2mo
Target deployment
Against 12–18 months for a traditional implementation.
1
Pilot running today
A handicraft manufacturer. Real workflows, real constraints.
We charge for savings, not seats.
No per-user licence, no module upsell. If the agents do not take work off the floor, there is nothing to bill. For an SME that has been sold shelfware before, that is the whole argument.
Why us
Two engineers who kept hitting the same wall.
- Systems thinking
- Civil and chemical engineering are both flows, constraints and bottlenecks. So is a factory.
- Indian manufacturing, first-hand
- Family business exposure to how purchasing here actually works, including what never reaches the ERP.
- We have shipped before
- Built products from scratch and put them in front of users.
How we got here
We built StartHub first: a platform for companies to find talent and collaborate. Then we spent months asking founders what actually slowed their businesses down. Nobody said hiring. They said the manual operational work no system was handling. That took us to ERPs, and to this.
Get in touch
See what this looks like in your operation.
We are pre-launch and working with a small number of manufacturers. If you run supply chain operations, or invest in people who do, we would like to talk.
Goes straight to the founders. We reply within a day.
support@kyros.net.in