Work with us

Bring us the problem. Keep the outcome.

This is what happens after you write to us: the four stages an engagement runs through, the shapes it can take, who you would be working with, and how to tell whether we are the right people for the problem.

How an engagement runs

Listen, design, build, prove. Four stages, in that order, every time: nothing is built before the problem is written down, and nothing is called a success before the number is measured.

01Week one
Listen
We sit with the people doing the work, not only the people buying the software.
What you get
- Problem statement
- Current-state map
- The baseline number
02Week one to two
Design
One page: the problem, the approach, and the number that will prove it worked.
What you get
- One-page brief
- Target architecture
- Priced increments
03Two-week increments
Build
Short, reviewable increments with the measurement wired in from the first release.
What you get
- Working software
- Tests and pipelines
- Progress against the number
04At every checkpoint
Prove
We compare the result against the number we agreed, and report it either way.
What you get
- Outcome report
- Runbook and hand-over
- The next decision

Three ways to engage

Most clients start with a review and grow from there. Each shape is priced openly.

See what each one costs

Review
Two weeks
A technology, cost or AI-readiness review with a written, prioritised recommendation. The cheapest way to find the number worth chasing.
Delivery
Per two-week 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.
Partner
Monthly
A fractional technology lead, or a team that runs and improves what we built: operations, cost, model drift, the next increment.

What you can hold us to

What stays true across every engagement, whatever it becomes.

Senior by default: Every engagement is led by someone who has shipped this kind of system before. No hand-off to a junior bench after the sale.
Small, whole teams: Two to five people who cover design, engineering, data and operations between them, so decisions are made in the room.
Stop at any checkpoint: Work is priced per two-week increment, so continuing is always your decision rather than a contractual obligation.
Reported either way: If the number did not move, you hear that from us first, with what we would do differently.
Yours to keep: Source code, infrastructure and documentation are handed over with every release. No lock-in to a stack, a vendor or to us.

Is it a fit?

Five honest questions. Tick what is true today and see where you land.

01There is a specific problem, not just a wish to "do something with AI".
02Someone on your side owns the outcome and can make decisions.
03You could name a number that should move if this works.
04We would get access to the people doing the work today.
05You are open to starting small and expanding on evidence.

Fit meter

0/5

Start with a two-week review.

When the problem is still forming, a short review is the cheapest way to find the number worth chasing.

Start a conversation

Where we are

Based in Jaffna, on the northern peninsula. Clients across the island, the Gulf, Europe and Australia, working in their time zones with regular overlap.

Jaffna. Where the work is built and handed over, on the northern peninsula.

Gopuram of the Nallur Kandaswamy temple, Jaffna

Nallur, Jaffna

Questions we are asked first

What kind of problems do you take on?

Anything where technology is the lever: a manual process eating hours, a system that no longer fits the business, a decision made on stale data, or an idea that needs a product built around it. If we are not the right fit we will say so in the first conversation.

How do engagements start?

With a free conversation, then a one-page brief: the problem, the approach we propose and the number that will show it worked. You decide from there. Most first engagements are two to six weeks.

Do you work with businesses outside Sri Lanka?

Yes. We are based in Jaffna, in the north of Sri Lanka, and work with clients across the island, the Gulf, Europe and Australia, in their time zones and with regular working overlap.

Who owns what you build?

You do. Source code, infrastructure and documentation are handed over with every release. There is no lock-in to us, to a vendor or to a stack.

How do you price work?

Short reviews and discovery work are fixed price. Builds are priced per two-week increment against an agreed scope, so you always know the cost of the next step and can stop at any point.

Can you take over an existing system?

Yes. Rescue and modernisation of systems that have become risky to change is a regular part of our work. We start with a review and a stabilisation plan before touching anything critical.