Skip to content
Saud Sajahan

Full-stack developer · Colombo, working globally

I turn complex workflows into useful software.

I help startups shape and build web products, dashboards, and connected services from interface to infrastructure.

EyesUnderstand the work

Start with the people, the task, and the friction. Then decide what to build.

HeadConnect the parts

Interfaces, APIs, and data should support the same clear product journey.

HeartMake it dependable

Give errors, access, and the small details the same care as the first screen.

A little further down

Every unnecessary step costs time.
I build the better path.

Understand the workflow. Make scope explicit. Build in reviewable steps. Test the product in real use.

More about me

Selected work

Built products and a clearly labeled mobile concept, each shown through the decisions behind it.

Guide Lanka product screenshot

Travel platform · 2025

Guide Lanka

Full-stack product build

A connected journey from finding a local guide to planning the visit.

Read case study
Inventory Management System screenshot

Operations dashboard · 2025

Inventory Management System

Dashboard and application build

A clearer view of stock and what needs attention.

Read case study

Mobile product · concept

Healthcare Booking

Independent concept design

A speculative mobile flow for finding an appointment and keeping the next step clear.

Read case study
Work

From idea to useful software

An example workflow; each project is scoped before work begins.

  1. 01First · initial conversation

    Discover the workflow

    We map users, tasks, and friction. You receive a short problem brief and priorities. Typically 2–5 business days.

  2. 02Next · before building

    Scope the first release

    We agree on the core journey, features, and review points. You receive a written scope and delivery plan. Typically 3–5 business days.

  3. 03During implementation

    Build and review

    I deliver reviewable increments around the agreed core journey.

  4. 04Finally · before handover

    Test and launch

    I test key paths, prepare handover, and launch after review.

The person behind the product

I work across interfaces, backend services, and the decisions that hold a product together.

More about me

A few things, answered.

What to expect before we talk about a project.

What should I send first?

A short description of the problem, who will use the product, and what a useful first version needs to do. The project brief helps you organize what you already know.

Do I need a complete feature list?

No. We can shape the scope together and prioritize the tasks users need to complete first.

Can you work on both interface and backend?

Yes. Depending on the project, I work across interfaces, APIs, data integration, access controls, and deployment.

What happens after I get in touch?

We review the workflow and constraints, agree on a clear scope, and break the build into reviewable steps.

Have something useful to build?

Tell me what you are working toward. We can turn the first conversation into a practical next step.

I reply within 24 hours.

Plan a project