Pricing
What it costs, before you ask.
Most technology partners will not give you a number until you are in a meeting. Here are ours: the shapes an engagement takes, what the work we are asked for most often starts at, and an estimator that puts an order of magnitude on your own problem.
Every figure is a starting point in Sri Lankan rupees, not a quote. What you are quoted is written down after one conversation about scope, and it does not move without your signature.
Three ways to engage
Pick the shape that fits the problem. Most clients start with a review or a first build and grow from there.
Two weeks
Review
from LKR 175k
Fixed price
A technology, cost or AI-readiness review with a written, prioritised recommendation. The cheapest way to find the number worth chasing.
- Interviews with the people doing the work
- Written assessment with options and trade-offs
- A roadmap with budget ranges
Per two-week increment
Most engagementsDelivery
from LKR 350k
Priced per increment
The core of what we do. We design, build, integrate and prove a solution against an agreed number, one reviewable increment at a time.
- Working software from the first increment
- Measurement wired in from day one
- Stop or redirect at any checkpoint
Monthly
Partner
from LKR 300k
Rolling, cancel with 30 days
A fractional technology lead, or a team that runs and improves what we built: operations, cost, model drift, the next increment.
- One to two days a week of senior time
- Monthly cost and reliability reporting
- Roadmap owned with you, not for you
Put a figure on your problem
Choose what is in scope and how much of it. The rack fills as you go, and the range moves with it.
Move the mouse to turn the stack. Click a slab, or use the list.Tap a slab, or use the list below.
Indicative starting range
LKR 300k to 400k
A starting point for this shape of work, not a quote. The figure we write down follows one conversation about scope.
Get this pricedWhat we are asked for most
Six pieces of work we have done more than once, and what each one starts at.
Workflow automation starter
One manual process, automated end to end and measured against the time it used to take.
from LKR 450k
- Process mapped with the people who run it
- Integration with the systems you already own
- Exception handling and an audit trail
- Before and after timing, reported
- Three months of support
- Asked for most
Document intelligence pipeline
Invoices, claims or contracts read, checked and posted without a person retyping them.
from LKR 750k
- Extraction tuned on your own documents
- Confidence thresholds with human review
- Posting into your finance or line-of-business system
- Accuracy measured per field, not per document
- Six months of model monitoring
Custom business system
The web or mobile system the off-the-shelf options keep almost fitting.
from LKR 850k
- Discovery and a written problem statement
- Design and build in two-week increments
- Your accounts, your repositories, from week one
- Load and security testing before launch
- Hand-over session and runbooks
Analytics foundation
One source of truth, and the three reports the business actually decides on.
from LKR 550k
- Sources consolidated into one warehouse
- Definitions agreed and documented
- Dashboards for the decisions, not for decoration
- Refresh automated and monitored
- Training for the people who will own it
Managed operations
We run and improve what has been built: uptime, cost, model drift, the next increment.
from LKR 300k per month
- Monitoring and on-call for what we operate
- Monthly cost and reliability report
- A budget of senior hours for changes
- Quarterly roadmap review
- Rolling, cancel with 30 days
Technology or AI review
Two weeks, one written recommendation, and the number worth chasing next.
from LKR 175k
- Interviews across the teams involved
- Systems, cost and risk assessed
- Options with trade-offs, not one answer
- A roadmap with budget ranges
- Credited against a build if you continue
In every price
- A senior lead who has shipped this kind of system before
- A written problem statement with a number attached, before any build
- Code, infrastructure and documentation in your accounts from week one
- Fortnightly demos of working software, not status decks
- The measurement that proves the number, reported as found
What moves the figure
- How many systems we have to integrate with, and how well they are documented
- Whether the data exists, and what state it is in
- Compliance, audit or residency requirements
- How much of the operation has to keep running during the change
- Whether your team takes over at hand-over or we operate it
Questions about money
Why ranges and not a fixed price?
Because a fixed price set before the problem is understood is either padded or wrong. The two-week review is fixed price and ends with a budget range you can take to a board. From there each build increment is priced individually, so you are approving a known amount each time.
What is the smallest sensible engagement?
The two-week review. It is the cheapest way to find out whether there is a number worth chasing, and its fee is credited against a build if you go ahead.
Can we stop partway?
Yes. Work runs in two-week increments and each one ends with something working and a checkpoint. You can stop, redirect or change the team at any checkpoint, and you keep everything produced up to that point.
Do you charge for the tools you build on?
No. Licences, cloud and model usage are billed to your own accounts at cost, and you can see them. We never resell infrastructure at a margin.
Are these figures quotes?
No. They are starting points that show the order of magnitude of each kind of work. A quote follows a conversation about scope, and it is written down before anything begins.
Bring us the problem.
A first conversation is free and usually enough to tell you whether this is a software, automation or AI problem, and what it would take to solve.