Process

No mystery, no three-month silence.

Most software projects go wrong in the same two places: nobody agreed what was being built and nobody said anything until it was late. Our process exists to close both gaps.

  1. 01

    Discover

    Usually 3–7 days

    We learn how you work today before suggesting how software should change it. For a shop that means standing at the counter; for a web project it means understanding who uses the thing and what they are trying to finish.

    You end up with

    • A written scope: what is included, what is not
    • A fixed price or a clearly bounded estimate
    • A milestone plan with dates
  2. 02

    Design

    Usually 1–2 weeks

    You see the screens before we build them. Changing a layout at this stage costs a conversation; changing it after the system is built costs real money. We would rather you be difficult here than disappointed later.

    You end up with

    • Screen designs for the main flows
    • A clickable walkthrough where it helps
    • Agreement on scope before any production code
  3. 03

    Build

    Typically 4–12 weeks

    Built in milestones you can open and try, not a long silence ending in a reveal. You get an update every week, in plain language, including the weeks when something took longer than planned.

    You end up with

    • A working build at each milestone
    • Weekly written progress updates
    • Your own access to the repository from day one
  4. 04

    Launch & support

    Ongoing

    We install it, train the people who will use it and hand over everything - code, credentials, documentation. Then we stay reachable, because the week after launch is when real questions appear.

    You end up with

    • On-site installation and staff training (local clients)
    • Full handover: code, data, accounts, documentation
    • An optional support plan - never a lock-in

05Working with us

How we communicate

  • WhatsApp for quick things, email for anything that should be on record
  • Slack, Teams or Jira if that is where your team already lives
  • A written update every week, whether the news is good or not
  • You talk to the engineers building it, not an account manager

After launch

  • A settling-in period where fixes are on us, not billed
  • Optional monthly support: updates, backups, small changes
  • You keep every credential and can leave at any time
  • Training materials so a new staff member can be taught without us

06FAQ

Working together: the practical questions

How do payments work?

Normally a deposit to start, then payments at agreed milestones, with the balance on handover. For retainers it is monthly. Everything is written down before any money moves.

What if I want to change something halfway through?

Small changes are part of the job and we absorb them. Anything that genuinely shifts the scope gets quoted separately before we do it, so you are never surprised by an invoice.

How often will I hear from you?

Weekly at minimum, in writing, plus whenever something needs your decision. If a week goes badly you will hear about that too - hiding problems only makes them more expensive.

Do you sign NDAs and contracts?

Yes to both. For overseas clients we work to a written agreement covering scope, payment, IP ownership and confidentiality before starting.

What timezone do you work in?

We are in Colombo, Sri Lanka, GMT+5:30. That is a working-hours overlap with the UK in our afternoon, Europe and the Middle East through the day and Australia in our morning. Calls outside those hours can be arranged.

Who owns the code when it is finished?

You do, outright. Handover includes the repository, the database, the hosting accounts and documentation. We do not hold anything back as leverage for a support contract.

Have a project in mind?

Tell us what you are trying to build. We will come back within one working day with an honest view of scope, timeline and cost.