Syncora

Process

How Syncora 
works 

Syncora runs client work as a scoped engagement from Colombo. You see the boundary before engineering starts, you review a staging site, and you know whether support continues after launch.

Last updated

Steps
06
Scope
Written
Review
Staging
Studio
Colombo

  1. Step 01

    Discover

    We start from a real job, not a feature list. You describe who is stuck and what done looks like. If we cannot name that, we do not start.

  2. Step 02

    Scope

    You receive a written boundary: what is included, what is not, the currency (LKR or USD), and how acceptance works. Chat history is not the contract.

  3. Step 03

    Design

    Structure first, then visual design. Empty, loading and error states are part of the work. The interface has to be buildable.

  4. Step 04

    Build

    A small team implements on a staging URL. Our usual stack is Next.js, NestJS, TypeScript and PostgreSQL. We say so if a project needs something else.

  5. Step 05

    Accept

    You review against the scope. A new idea is a change. We would rather write the change down than hide it inside the original fee.

  6. Step 06

    Hand over

    You receive the system you agreed, the source as the agreement states, and a named path for support or a clean end. Accounts that should be yours are in your name.

Proof we can show

Staffora is the product we operate in public. Client names, logos and outcome figures are published only when that client agrees. Until then, this page will not invent them. TODO: add approved case studies here, with the metric the client is willing to stand behind.

Questions people ask

How does a Syncora project start?
With a conversation and a written scope. We would rather decline a fuzzy brief than start a build we cannot accept against. You will know what done means before engineering begins.
Who do we work with?
A small senior team. Samitha Kannangara leads technology. You will not be passed through a rotating cast without an introduction.
How are changes handled?
A change that alters the agreed outcome is written down and priced or swapped. We do not absorb an open-ended wishlist inside a fixed scope.
Do you show work in progress?
Yes. You review a staging environment. Feedback is against the scope, not against a new idea that arrived in the same week, unless we agree to change the scope.
What do we receive at the end?
The deployed system described in the scope, the source as agreed, and a handover of how to operate it. Accounts that should be in your name are in your name.
What happens after launch?
Either a support agreement or a clean end. We will not leave you without saying which of those it is.

Related