Pricing

What automation should cost you.

Not a rate card. What drives the price, what three real budgets deliver, when you’d need us to keep running it, and whether it’s worth doing at all.

What decides the price

Five things move the number.

None of them are about which tool we use. They’re about how much the workflow actually has to handle.

FactorKeeps the cost downPushes the cost up
Workflows involvedOneSeveral, that need to work together
Systems connectedOne or two you already useFive or more, including older systems without a modern connection
Judgement requiredFollows a fixed ruleGenuine judgement calls on messy, ambiguous input
Data qualityClean, structured, in one placeScattered across systems, inconsistent formats
Who sees the outputInternal use onlyCustomer-facing, or touches money

Three budgets

What each budget should deliver.

Reference points, not a fixed menu. Most projects sit somewhere between them, and we scope every one individually.

Entry S$3,000

One workflow, one problem.

Example An AI that reads incoming enquiries and logs them to your CRM.

  • A discovery call to map the workflow
  • One system integration
  • The automation itself, tested against real examples
  • Handover and light documentation

Best fit when You want to prove automation is worth it before committing further.

Typical SME project S$12,000

An end-to-end process across your team.

Example Full enquiry-to-quote: read the message, check stock, price it, send it, follow up if it goes quiet.

  • Everything at S$3,000, plus:
  • Several integrations across your systems
  • Exception handling for the cases a rule can’t cover
  • A monitoring dashboard
  • Training for your team

Best fit when One team’s workload genuinely needs to shrink, not just one task.

Enterprise & consultancy S$20,000+

A business-critical system, or a strategy engagement.

Example A multi-department rollout, or a private AI model trained on your own data.

  • Everything at S$12,000, plus:
  • Advanced permissions and audit trails
  • Dedicated support and a named point of contact
  • Regulatory or compliance requirements built in from the start

Best fit when Automation has to coordinate across systems or departments, or the data involved is regulated.

Before you decide

The questions everyone asks.

Do I need engineers on my own team?

No. We scope, build and hand you something your team can run day to day without writing or reading code.

What happens if it gets something wrong?

It stays supervised until you’re confident in it, and every action is logged so we can see exactly what happened and why.

Will it work with tools we already pay for?

Yes. We build inside your existing stack first — Zapier, Make, whatever you’re already on — before ever recommending something new.

Is our data safe?

Each automation only ever sees the specific data its one job needs, and every permission is enforced on our servers, not just hidden behind a button.

How fast can we actually start?

A scoped, fixed-price build for one workflow is typically ready in a few weeks from the discovery call.

If we stop working together, do we keep it?

Yes. Anything built on your own infrastructure is yours to keep, whether or not we keep working together.

Do you work with businesses outside Singapore?

Yes. We’re based in Singapore and work with companies across APAC and beyond, mostly remotely.

Can you take over automations someone else built?

Yes. We review what’s running, fix what’s fragile, and can look after it under a care plan from S$300 a month.

What do I need to prepare before the first call?

Nothing formal. One or two repetitive tasks in mind, and a rough idea of how many hours they take each week, is plenty.

Is the first call really free?

Yes. The 30-minute call is free with no obligation, and you’ll leave knowing what to automate first and roughly what it would cost.

Mission-critical or not?

How much it matters if it’s wrong.

This, more than anything, decides whether a one-off build is enough or you need us watching it after launch.

Internal, low-stakes

Meeting summaries, internal reminders, a first draft someone checks anyway. Occasional errors are fine, and a person reviews anything that looks off. Rarely needs a retainer.

Customer-facing, or touches money

Quotations, payments, anything compliance-sensitive. This needs validation, an approval step, monitoring and an audit trail from day one. One good test run proves very little about a thousand real conversations.

The real cost

It’s the hours, not the build.

Say four people each lose six hours a week to one repetitive task. That’s roughly 1,150 hours a year, gone. At a fully loaded S$28 an hour, that’s over S$32,000 a year, whether or not you ever fix it. A S$12,000 build that removes only half of it still pays for itself well inside a year. Run your own numbers:

Automation return estimator

3
8 h
30
40%
Value per monthSGD 1,247
Hours freed per month42
Value per yearSGD 14,964

A planning estimate from your own inputs, not a quote or a guarantee. It leaves out benefits that are harder to count, such as fewer errors. Nothing you enter leaves this page.

Retainers

When we need to keep running it.

Not every project needs one. A simple, internal workflow can be handed over with documentation. A retainer earns its cost when:

  • It’s customer-facing, or touches money, and needs regular monitoring.
  • It depends on integrations or APIs that change over time and need updating.
  • Your process keeps evolving, and the automation needs to evolve with it.
  • You want a named person watching it, not just hoping it keeps working.

How we bill

Fixed project fee

A well-defined build with a clear scope.

One agreed fee, paid once.

Care plan retainer

An automation that needs regular watching after launch.

From S$300/month, scoped to how many systems need watching and how fast issues need to be caught.

Hybrid

A build now, with support built in from day one.

A fixed fee for the build, plus a care plan from launch.

Is it worth automating?

Three or more of these? Let’s talk.

We’d rather talk you out of a build than sell you one you don’t need.

  • Someone on your team could describe the task in a few sentences, start to finish, without “it depends.”
  • It comes up daily or weekly, not once a quarter — the hours actually add up.
  • Getting it wrong or late has a real cost attached: a lead that goes cold, a customer who chases you, a number that has to be right.
  • The information it needs already lives somewhere digital — an inbox, a sheet, a system you already use.
  • If it disappeared tomorrow, your team could take on more work without you hiring for it.

Pricing FAQ

Still deciding?

Do I need a retainer for every project?

No. A simple, internal, low-stakes workflow can be handed over at the end of the project with documentation, and your team runs it from there. A retainer earns its cost once an automation is customer-facing, touches money, or depends on integrations that change over time.

How is the S$12,000 typical project different from the S$3,000 entry tier?

Scope, mostly. S$3,000 proves one workflow works. S$12,000 covers a full process end to end, across several systems, with exception handling for the messy cases a single rule can’t catch, plus a dashboard and training so your team can see it working.

What if my project doesn’t fit neatly into one of these three bands?

Most don’t exactly. These are reference points, not a fixed menu. We scope every project individually on a free 30-minute call, using the same factors above — how many workflows, how many systems, how much judgement, how clean the data, and how much it matters if it’s wrong.

Can I start small and expand later?

Yes, and we’d usually recommend it. Starting with one entry-tier workflow lets you see real results before committing to a larger, multi-workflow build.

Are running costs included in the project price?

No. The project fee covers scoping, building, testing and handover. Running costs, such as AI model usage, hosting and any tool subscriptions your automation relies on, are billed by those providers. We estimate them for you while scoping, so you see the full picture before you commit.

What does a care plan include?

Care plans start from S$300 a month and are scoped to how many systems need watching and how fast issues need to be caught. Typically that means monitoring, fixing anything that breaks, updating integrations when a connected app changes, and a monthly health review of what each automation is doing.

What happens if the scope changes halfway?

Changes are normal once a build starts and real data shows up. We scope the change, quote it up front, and only proceed once you agree, so the price never moves without your say-so.

Can we see it working before paying for a bigger build?

Yes. Start with one entry-tier workflow and run it in shadow mode first, where it works silently on real data so you can compare what it would have done before it takes a real action. Expand once you’ve seen the results.

How do invoices and payment work?

Project fees are invoiced as set out in our Terms & Conditions of Sale; invoices are payable within 21 working days unless your quote says otherwise. Care plans are billed monthly.

Can the Enterprise Development Grant be used for this?

Often, yes. EDG can co-fund up to 50% of a qualifying project, or up to 70% for qualifying SMEs. Enterprise Singapore assesses each application, and the criteria change, so check them before you budget. We help prepare the application once your project is scoped.

Free consultation

Get 30 minutes with our experts.

Explore how AI can automate your most complex workflows. No obligation, just a clear plan for what to automate first.