Software shaped around how your business actually works

The problems

What usually brings people to us.

You are paying for software and still running the real work in spreadsheets

That gap is the sign that the package does not fit. The spreadsheet is the actual system, and it has no permissions, no audit trail and one person who understands it.

The process that makes you money is the part no package supports

Bespoke pricing, credit terms, multi-branch transfers, commission splits. These are usually the reason a business wins, and the reason generic software cannot be made to work.

Your data is scattered across systems that do not talk

Sales in one place, stock in another, accounts in a third, and someone re-keying between them. Every hand-off is a chance to introduce an error nobody catches until month end.

A previous developer disappeared

The most common story we hear. We work in stages with written scope, and everything is documented and handed over so the system is not hostage to one person — including us.

What you get

Deliverables, not a feature list.

• Written scope

  A document describing what will be built, what will not, and what it costs — agreed before development starts.

• Screen designs

  You see and approve the interface before anyone writes the code behind it.

• The build, in stages

  Working software you can open and use at each stage, not a progress percentage in an email.

• Data migration

  Your existing records brought across and reconciled, not left behind in the old system.

• Training and documentation

  Your team trained on site, and written documentation that survives staff turnover.

• Handover

  Source code, database and deployment documented and handed to you. You own it.

Process

How it runs, and how long it takes.

1. 01

   Discover

   We map the current process end to end, including the parts held together by memory and WhatsApp.

   1–2 weeks

2. 02

   Design

   Screens, data model and written scope, with a fixed price against it.

   1–2 weeks

3. 03

   Build

   Delivered in reviewable stages so you can redirect early instead of at the end.

   6–16 weeks

4. 04

   Test and launch

   You test with real data before go-live. We run alongside the old process until you are confident.

   1–2 weeks

5. 05

   Support

   Annual maintenance covering updates, backups, security patches and small changes.

   Ongoing

Timings are the ranges we actually see, not best cases. We confirm yours in writing at the design stage before you commit.

Built with

The stack.

• Web-based
• Cloud or on-premise
• Role-based access
• Audit trails
• API integrations
• Automated backups

Your data is yours and exportable at any time — see pricing for what support and hosting cost after launch.

Questions

What people ask before starting.

How much does custom software cost?

It depends entirely on scope, which is why we scope before quoting rather than guessing on a call. As a floor, we do not take on custom projects under LKR 60,000 — below that a template plus hosting genuinely serves you better, and we will say so.

How do payments work?

50% to start, 40% when you have tested and accepted the build, 10% at go-live. You are never paying for work you have not seen.

What if we need changes later?

Small changes are covered by the maintenance arrangement. Larger additions are quoted as their own piece of work, with a change-order reference so nothing is ambiguous.

Do you work with clients outside Sri Lanka?

Yes. We work with clients abroad who want serious engineering without London or Singapore rates.