Skip to content
teamsleek.ai

Modules · AI ERP

ERP modules with AI agents inside

The six modules of the AI ERP we build, each with agents that prepare the work and people who approve it. Start with the one that hurts most, then add the rest phase by phase on the same database.

Book a scoping call See the AI agents

Approval queue

5 waiting

  • Sales

    Quote Q-2611 for Corallis Fit-Out

    Drafted by the quotation agent

    S$1,097.63Review

  • Purchasing

    PO-0418 to Meridian Fasteners

    Drafted by the purchase order agent

    S$730.30Review

  • Inventory

    Goods receipt GRN-0932, 2 boxes short

    Drafted by the document intake agent

    33 boxesReview

  • Finance

    Bill for INV-77120, credit note drafted

    Drafted by the AP invoice agent

    S$684.52Review

  • Finance

    Reminder to Verano Kitchens, 74 days

    Drafted by the collections agent

    S$9,722.80Review

One queue for every module, routed by your approval rules.

Sample data. Harbourline Supplies Pte Ltd is not a real company.

The modules

Six modules, each with its agents

Each module is built around how your team works. The agents inside draft records, and a person approves them before anything changes.

There are six agents in all. Some work in more than one module: the document intake agent, for one, reads documents for sales and quotations, inventory, projects and service and job cards.

How modules connect

The modules share one database, approval queue and log

Modules are not separate apps glued together. A goods receipt in inventory is the same record finance matches a supplier bill against, and every agent draft waits in the same queue.
  1. Sales and quotationsUses 2 agents
  2. PurchasingUses 1 agent
  3. InventoryUses 2 agents
  4. FinanceUses 2 agents
  5. ProjectsUses 2 agents
  6. Service and job cardsUses 2 agents

Shared by every module

One database

Entered once, used by every module. No copies to keep in step.

  • Customers
  • Suppliers
  • Items
  • Projects
  • Documents
  • Users and roles

One approval queue

Drafts from every agent wait in one place, routed by your approval rules.

  • Q-2611Sales
  • PO-0418Purchasing
  • INV-77120Finance

One log

Who prepared it, who approved it, what changed and when.

  • 07:00 PO-0418 drafted, purchase order agent
  • 10:51 PO-0418 approved, operations manager

Sample data. Harbourline Supplies Pte Ltd is not a real company.

One order through four modules

Agents prepare each step. People decide at each step that matters. Nothing is typed in twice.

  1. Agent prepares

    Quote drafted

    Sales: account prices, stock checked

  2. Person decides

    Order confirmed, stock reserved

    Sales and inventory

  3. Agent prepares

    PO drafted for the shortfall

    Purchasing

  4. Person decides

    PO approved

    Purchasing

  5. Agent prepares

    Receipt drafted, bill matched

    Inventory and finance

  6. Person decides

    Bill approved

    Finance

First phase

What usually goes in a first phase

This is how we usually suggest scoping, not a rule. Your written phase plan sets the actual scope and price before you sign.
  1. 1

    Start where work is re-keyed or chased

    The module where your team copies data between systems, or chases people for answers, usually pays back first.

  2. 2

    One part of the business, end to end

    A first phase usually covers one flow from start to finish, such as enquiry to delivery or claim to payment, rather than a little of everything.

  3. 3

    Keep what works

    If your accounting package does its job, it can stay while operations move first. Finance joins when it is worth it.

Price bands

  • Quick build

    2 to 3 days of build

    From S$15k

    One workflow or one agent, on your data.

  • Build

    4 to 5 days of build

    S$30k to S$40k

    A set of modules and agents around one part of the business.

  • Enterprise programme

    Months, in phases

    Around S$150k

    A full ERP programme, delivered phase by phase.

See what each band includes

FAQ

Questions about modules

Do we need every module?

+
No. Most companies start with the module where the most re-keying and chasing happens, then add the rest phase by phase. Each new module joins the same database, approval queue and log.

Can we keep our accounting system?

+
Yes. Many companies keep their accounting package for the ledger at first and move operations into the new system. We check what your package allows on the scoping call and put the connection in the phase plan.

Can you add a module we don't see here?

+
Yes. We build around your process, so a module for something else, such as HR and claims, rental or quality checks, is scoped like any other phase. We list a module on this site only once we have built it and can show it on sample data.

Are the modules separate apps?

+
No. They share one database, so a customer, item or project is entered once and every module uses the same record. Agent drafts from every module wait in one approval queue.

Who owns the modules once they are built?

+
You do. You own the full source code of what we build, and there are no per-user licence fees. We keep our internal build engine and tooling. You can run the system on our hosting or in your own cloud account.

What does a module cost?

+
It depends on scope, so we price phases rather than modules. One workflow on your data can be a Quick build from S$15k. A set of modules and agents around one part of the business is a Build of S$30k to S$40k. A full ERP programme is around S$150k, delivered in phases.

Start with the module that hurts most.

Bring one workflow and a sample export. In 30 minutes we show how it would run as an approval queue on sample data, and what a first phase would cost.

Book a scoping call See pricing