Skip to content
teamsleek.ai

How we work

How we build, hand over and keep improving your system

Start with a 30-minute call about one workflow. Build in phases, with working software to try as we go. Test, migrate and go live, with us on hand after go-live. You own the full source code, and you can keep us to run and improve it if you want.

Book a scoping call See pricing

Phase plan · v2

In progress

Phase 1: Quotations, purchasing and stock

Harbourline Supplies Pte Ltd

Scope
Quotations, purchasing and stock by location. Quotation and purchase order agents, both drafting for approval.
Price
S$36,000, fixed for this scope (Build band)
Acceptance
The criteria in this plan, run by your team and signed off by your finance manager
  1. DoneWeek 1Spec agreed, build starts
  2. DoneWeek 2Working software for your team to try
  3. In progressWeek 3Our test plan, then your acceptance testing
  4. PlannedWeek 4Migration dry run and reconciliation
  5. PlannedWeek 5Training, then go live
  6. PlannedAfterGo-live support, for the period in this plan
  7. PlannedHandoverSource code, docs, credentials, walkthrough

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

The steps

From one call to a system you own

Eight steps. Each one says what you bring and what we do. The dates for yours are written into your phase plan.

  1. Step 0

    Scoping call

    30 minutes

    30 minutes on one workflow, a sample export and who approves what today.

    You bring

    • One workflow that costs you time or money
    • A sample export: a spreadsheet or report from today's system
    • Who approves what today

    We do

    • Walk through the workflow with you
    • Show it running as an approval queue on sample data
    • Follow up with a written phase plan: scope, price and dates

  2. Step 1

    Quick build

    From S$15k · 2 to 3 days of build

    Optional first step: one workflow or agent on your data, from S$15k.

    You bring

    • A real export for that one workflow
    • One person who knows the process and can answer questions
    • Time to try it and tell us what is wrong

    We do

    • Build the workflow, and its agent if it has one, on your data
    • Show it to your team and let them use it
    • The code is yours, like everything we build for you

  3. Step 2

    Build

    Working software as we go

    Modules and agents built in phases, with working software shown as we go.

    You bring

    • Decisions on the spec, from the person who owns the process
    • Quick answers to our questions, so the build is not held up
    • Your people at the demos set in your phase plan

    We do

    • AI coding agents write the code and tests, using our build tooling
    • Our tester, our ERP controller and Lester check every change
    • Show you working software as we go. The demo rhythm is set in your phase plan

  4. Step 3

    Test

    Three gates

    Our test plan, then your acceptance testing, then your sign-off.

    You bring

    • People who do the work today, to run the acceptance tests
    • Real scenarios, including the awkward ones
    • A sign-off when it passes

    We do

    • Run our test plan and fix what fails
    • Support your acceptance testing and fix what you find
    • Record the results, so you sign off on evidence

  5. Step 4

    Migrate

    Dry run first

    A dry run, then balances and open items moved and reconciled with you.

    You bring

    • Exports from the systems you use today
    • A finance person to check the reconciliation
    • Your sign-off on the reconciled figures

    We do

    • Map and load your data in a dry run
    • Reconcile opening balances and open items: unpaid invoices, open orders, stock on hand
    • Repeat until it ties out, then load it for real

  6. Step 5

    Go live

    Training, then switch-over

    Your team trained and the system switched on, with us on hand.

    You bring

    • A go-live date that suits the business
    • Time for your team to be trained
    • A team ready to use it from day one

    We do

    • Train your team on the system before it is switched on
    • Switch over and watch the first days closely
    • Stay on hand after go-live. The support period is set in your phase plan

  7. Step 6

    Handover

    Code, docs, credentials, walkthrough

    Source code, documentation and credentials for what went live.

    What you own

    You bring

    • The person on your side who should hold the code and the admin access

    We do

    • The full source code, including the core code it runs on
    • Documentation and a runbook
    • Admin credentials
    • A recorded walkthrough of the system

  8. Step 7

    Run and Evolve

    After go-live, if you want them

    Hosting and support, plus monthly build time for changes, if you want them.

    Run and Evolve

    You bring

    • A list of what you want next, in your order of priority

    We do

    • Run: hosting, support and AI usage, on the terms in your Run agreement
    • Evolve: monthly build time for changes and new workflows

Who you work with

Three people, and what each one checks

TeamSleek is the AI ERP team at SleekDigital in Singapore. AI coding agents write the code. Three people check it, and one of them releases it.
Lester Law

Lester Law

Founder

Runs the AI coding agents and reviews every release. Nothing ships without his release.

What they check

  • The change does what the spec says
  • It passes our review checklist
  • It is safe to release to your team

Our tester

Testing

Runs the test plan on every build, by hand and with the automated tests, and sends back what fails until it passes.

What they check

  • Every screen and every role in the spec
  • The awkward cases, not only the happy path
  • That fixed problems stay fixed

Our ERP controller

Business rules

Checks the business rules on every change that touches money or stock, the way your finance team would.

What they check

  • GST, credit terms and approval limits
  • What each step posts to stock and the ledger
  • Balances and open items during migration

How AI builds the code

Who writes, checks and releases the code

We build with AI coding agents and our own build tooling. That is why the build takes days. The checks around it are why you can trust what comes out.
  1. Step 1

    Spec

    You and Lester

  2. Step 2

    Code and tests

    AI coding agents

  3. Step 3

    Test plan

    Our tester

  4. Step 4

    Business rules

    Our ERP controller

  5. Step 5

    Review and release

    Lester Law, founder

Our build tooling

Our tooling means a new system starts from parts we have already built and tested, not a blank page. Agents write the code for your workflow with it, with tests, to a spec you agreed.

  1. 1

    Generators

    They start each system and module from parts we have built and tested before: users and roles, records and approval steps. The code they produce goes into your source code, like the rest.

  2. 2

    Module patterns

    How a new module is laid out, tested and documented, so every module reads the same way.

  3. 3

    Agent instructions

    How our AI coding agents write code, tests and docs to our standard. Lester runs the agents and steers the work.

The tooling stays with us. The code it produces, including the core code your system runs on, is in the source you own: see what you own.

Build log · Purchasing · release 0.4

  1. Mon 09:10LesterSpec v3 agreed: 9 screens, 14 rules
  2. Mon 16:45AI agentWrote the code: 31 files changed, 58 tests added
  3. Tue 10:05Tests58 passed, 0 failed
  4. Tue 15:20TesterTest plan: 23 of 24 cases passed. Sent back 1: approval email shows the amount before GST
  5. Tue 17:10AI agentFixed, with a new test: 59 passed, 0 failed
  6. Wed 10:30TesterRe-run: 24 of 24 cases passed
  7. Wed 11:40ControllerGST 9% on every line. Approval limits match the spec
  8. Wed 17:30LesterReviewed against the checklist. Released 0.4

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

The review checklist

Every release, before Lester releases it

  • It does what the spec says and passes its acceptance tests
  • Automated tests cover the new rules, and they pass
  • Our tester has run the test plan, and every failure is fixed
  • Our ERP controller has checked tax, limits, stock and ledger effects
  • By default, agents draft and a person approves
  • Each role can see and do only what the spec allows
  • No passwords or keys in the code, and inputs are checked
  • The docs and the runbook are updated for the change

What you own

What you own, and what we keep

You own the full source code of what we build for you. There are no per-user licence fees, so you can add staff without adding fees.

Yours

  • The full source code of what we build for you, including the core code it runs on
  • Your data, and the database it lives in
  • The automated tests written with the code
  • The prompts and limits each agent works to, with their tests
  • Docs: how to set it up, how it fits together, and a runbook for running it
  • Admin credentials for the system
  • A recorded walkthrough of the system
  • The choice of where it runs: our hosting or your own cloud account

What we keep

Our build tooling: the generators, the module patterns and the instructions our AI coding agents follow. It is how we build quickly. The code it produces for you, including the core code your system runs on, is part of the source you own.

Your repository

Owned by you
  • harbourline-erp/
  • ├─ core/# users, roles, records, approval steps
  • ├─ app/# screens and business logic
  • ├─ db/# tables, and every change to them
  • ├─ agents/# prompts, limits and when each agent stops
  • ├─ tests/# the automated tests
  • └─ docs/
  • ├─ README# how to set it up
  • ├─ architecture# how it fits together
  • └─ runbook# how to run it day to day

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

If we disappear

If we disappear, another team can take over

We are three people, so it is a fair question. The answer is that you already hold everything another team would need, including the core code your system runs on.

You hold the code

The full source code of what we built is yours, including the core code it runs on. Any developer you choose can open it and change it.

You hold the docs and runbook

How it is set up, how it fits together and how to run it day to day are written down and handed over with the code.

It is a standard stack

A modern TypeScript web stack and a standard database, so another team can read the code and keep building.

You can move it

You can run the system in your own cloud account instead of on our hosting.

What stays with us is how we build: the generators, module patterns and agent instructions. Another team works on your code directly and does not need them. Ask us on the scoping call what a handover to another team would look like for your system, and we will walk you through it.

Run and Evolve

After go-live: Run keeps it going, Evolve keeps it improving

Two monthly retainers, offered after go-live if you want them. What each one covers, and its price, is written into your phase plan.

Run

Keep it running

  • Hosting. On our hosting, or in your own cloud account.
  • Support. Your team has people to ask when something is not right, on the terms below.
  • Fixes. Problems found after go-live are fixed under Run.
  • AI usage. The AI usage your agents and AI features need to do their work.

Evolve

Keep improving it

  • Monthly build time. A set amount of build time each month for changes, new workflows and new agents.
  • One request queue. You put requests in your order of priority. We size them and build from the top.
  • Same checks. Every change goes through the spec, tests, rules check and Lester's release.

Evolve requests · this month

Your order
  1. 1Stock report by warehouseReleased
  2. 2Supplier portal: upload delivery ordersIn test
  3. 3Collections agent: weekly overdue summaryBuilding
  4. 4Customer price breaks by quantityQueued

Each request goes through the same spec, tests, rules check and release.

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

Support under Run

What your Run agreement sets out

Each of these is agreed with you and put in writing before go-live, so you know how support works before your business depends on the system.

If the system runs in your own cloud account, the agreement also says which parts your team looks after and which we do.

  • Support hours and channels

    When we are available, and how your team reaches us.

  • How issues are raised and handled

    How your team reports a problem, how we decide what comes first, and how you hear back until it is fixed.

  • Backups and monitoring

    What is backed up, how a restore works, and what we watch so we hear about a problem early.

  • Security updates

    How the system, the libraries it uses and its hosting are kept up to date.

  • Cover when someone is away

    We are three people, so the agreement names who looks after your system when one of us is on leave.

Because you own the code, you can also run the system in your own cloud account and have other developers change it. See pricing for the build bands.

What weeks means

Why a build of days still takes weeks to go live

The build is fast because AI coding agents write the code: 2 to 3 days for a quick build, 4 to 5 days for a build. The weeks around it are for the spec, testing, migration and go-live, and they need your team's time as well as ours.

Illustration, not to scale

If you apply for the EDGE Grant

The application comes first. It must be made before any work starts or any payment is made. For vendors that are not pre-approved, the official page gives about 10 weeks to an outcome.

Your phase

  1. Spec

    agreed in writing

  2. Build

    days, by AI coding agents

  3. Test

    our plan, then yours

  4. Migrate

    dry run, reconcile

  5. Go live

    training, switch over

  6. After go-live

    support, for the period in your plan

Your own dates are written into your phase plan before you sign.

Dates in your phase plan

Your phase plan sets out the scope, the price, the acceptance criteria and the dates for each step before you sign. You see working software as we go. The demo rhythm is set in your phase plan.

Grant timing

An EDGE Grant application must come before any work starts or any payment is made. A fast build and the grant process pull against each other, so decide per project. Read our EDGE guide or the official EDGE page.

For comparison

Panorama Consulting's 2026 ERP report, a survey of 170 organisations, puts the median ERP project at 9 months, across all vendors. The report is a gated download, so the figure here is taken from the erpresearch.com summary (checked 10 Nov 2026).

FAQ

Questions about how we work

How long does a phase take?

+
Your phase plan gives the dates before you sign. The build itself takes days: 2 to 3 days for a quick build, 4 to 5 days for a build. The rest of the phase is the spec, testing, your acceptance testing, migration and go-live, which need your team's time as well as ours.

What do you need from us?

+
One person who owns the process and can make decisions on the spec, people who do the work today for acceptance testing, a finance person to check the migration, and exports from the systems you use now. Each step above lists what you bring.

When can you start?

+
We confirm a start date in your phase plan. We take on a limited number of builds at a time, so the date depends on what is already under way. Ask on the scoping call and we will tell you where things stand.

What does the agreement look like?

+
A written phase plan with the scope, the price, the acceptance criteria and the dates for each step. You can ask for our standard terms before you sign.

When do we get the source code?

+
You own the full source code of what we build for you, including the core code it runs on. It is handed over at the handover step with the documentation, the admin credentials and a recorded walkthrough. Your phase plan says when that falls for your project. If you need the code at other points, tell us on the scoping call and we write it into the plan.

How are our people trained?

+
Training is part of go-live: we train your team on the system before it is switched on. The people who ran your acceptance tests will have used it already. At handover you also get the documentation and a recorded walkthrough, for people who join later.

Who fixes problems after go-live?

+
We do. Fixes after go-live are covered by Run, or as agreed in your phase plan if you do not take Run. Support hours, how your team reaches us and how issues are handled are written into the Run agreement before go-live.

What if the AI model provider changes?

+
The prompts, limits and tests for each AI feature sit in your code. So switching to another model or provider is a contained piece of work, and we agree it with you before anything changes.

Do we have to take Run and Evolve?

+
No. They are offered after go-live and priced in your phase plan. Because you own the code, you can also run the system in your own cloud account and have other developers change it. See if we disappear.

Can we use the EDGE Grant?

+
Maybe. Enterprise Singapore's EDGE Grant replaced EDG, PSG and MRA from 30 Sep 2026. You must apply before any work starts or any payment is made, and vendors cannot apply for you. We can't promise a grant outcome or percentage for your project. Our EDGE guide has what may apply and the official links.

Do you charge per user?

+
No. You own the code, so there is no per-user licence fee. Add staff without adding fees. Our bands are on the pricing page.

Start with one workflow.

In 30 minutes we walk through it with you, show it running as an approval queue on sample data, and tell you what a first phase would cost.

Book a scoping call See pricing