Skip to content
Sun Software logo with the tagline Engineering Beyond Code
How we work

How your project runs, from the first call to after launch.

Every project goes through the same six steps. At the end of each one you get something you can look at and check, so you always know where your website or app stands.

your-project-plan6 steps
  • DiscoverWritten brief
  • DesignApproved proposal
  • BuildWorking draft
  • ValidateTest results
  • LaunchLive site or app
  • OperateSupport plan
Why we work this way

Fast is good. Fast with no checks is a gamble.

When a project starts without a written brief, set points where you check the work, or a plan for going live, nobody is sure what is being built. That is hard on you, and on the people building it.

Our one rule

Every step ends with something you can check. We don’t move on until you have.

The six steps

What happens at each step, and what do you get?

The steps are the same on every project. A small job gets a short version of each one.

Stage 01

Discover

We learn what you want to achieve, who will use it, what you already have and what limits we have to work within.

What we do

  • Talk to you and the people on your side who decide
  • Write down who uses it, how the work flows and which tools you already use
  • List what we are assuming, what we don’t know yet and what could go wrong

You get

A written brief you can read and correct: your goals, your users, how the work flows, what we assumed and the risks.

Your part

Tell us what a good result looks like, and let us talk to the right people and see the tools involved.

Stage 02

Design

We plan how it will be built and in what order. Where there is a choice, we show you what each option gains and costs.

What we do

  • Decide what information it stores, which tools it connects to and who is allowed to see what
  • Write down how it will be protected and where it will be hosted
  • Split the work into stages, each with a plain test for “done”

You get

A proposal: what is included, notes on how it will be built, the stages, the test for “done” at each stage and the price.

Your part

Look at the options and approve what is included before we build anything.

Stage 03

Build

We build in stages you can look at. Every change is recorded, so we can always see who changed what and when.

What we do

  • Keep a full history of the code from the first day
  • Have a second engineer read every important change, whether a person or an AI tool wrote it
  • Show you progress on a private test copy at the reviews we agreed

You get

Something working that you can click through at every review, and a written update every two working days.

Your part

Join the reviews, answer our questions and tell us if your priorities have changed.

Stage 04

Validate

We test what we built against what you approved.

What we do

  • Test each feature against the test for “done” in your proposal
  • Check the parts that handle logins, payments and private data, and what happens when something fails
  • Check speed, and ease of use for people with disabilities, where your project includes it

You get

Test results set against what you approved, with any open issues listed.

Your part

Try it yourself on the private test copy and tell us in writing that you’re happy.

Stage 05

Launch

We put it live step by step, and hand over everything you need to own it.

What we do

  • Follow a written go-live checklist
  • Take a backup, put it live and check that it works
  • Keep a way to undo the release ready

You get

Your live website or app, your own access to it and the written notes on how it works.

Your part

Approve the go-live date and confirm who holds each account.

Stage 06

Operate

We look after it and improve it under a support plan, if you choose one.

What we do

  • Watch it, fix issues and keep it up to date
  • Write up anything that goes wrong, and why it happened
  • Plan improvements with you

You get

A support plan that says in writing what is covered and how quickly we respond.

Your part

Choose a support plan, or run it yourself with the handover pack.

What you get in writing

Six documents you can hold us to

Each one is written for you, the person who approves the work. You don’t need to be technical to read them.

Document 01

Project brief

Your goals, your users, how the work flows, what we assumed and the risks, in plain words.

Document 02

Proposal

What you get, the stages, the test for “done” at each stage, the price and who is responsible for what.

Document 03

Risk list

What could go wrong and what we don’t know yet. Each item has a named person and a plan.

Document 04

Test report

What we tested, what we tested it against and what is still open.

Document 05

Go-live checklist

The steps, the backups and the way to undo it, for each release.

Document 06

Handover pack

The written notes, your access and a record of the main decisions.

How we use AI

We use AI tools. A person checks the work.

We use AI tools where they make the work faster and better. They never approve their own work.

Our engineers work with Cursor and models from OpenAI, Anthropic and Google, under a written policy.

  1. 1

    They work inside your project

    AI tools work inside your project’s own code, so what they suggest fits what is already there.

  2. 2

    They can’t go live on their own

    AI tools never hold the logins to your live site or app. They never approve a change or put it live by themselves.

  3. 3

    People check every change

    One engineer answers for every change, and a second engineer reads it.

  4. 4

    No passwords or personal data

    Passwords, keys and personal data never go into any AI tool.

  5. 5

    Your choice

    You can ask us not to use AI tools on your project.

Working together

What is it like to work with us day to day?

You always know who to talk to, what has been done and what happens next.

What this way of working can’t promise

No way of working removes every issue. Ours makes problems rarer, easier to spot early and cheaper to fix. The checks we run are matched to the size of your project and written into your agreement.

  • One named contact. One named person is responsible for the result and for answering you.

  • Regular written updates. What we did, what comes next and any open questions, every two working days.

  • Hours when we are both online. At least 4 hours a day overlap with UK and US East Coast working hours.

  • A review at the end of each stage. You see it working and decide what happens next.

  • Changes in writing. Want a change? We tell you what it adds to the work, the time and the price. We start once you approve it.

  • You know who you are signing with. Our team manages the work from Pakistan. Your proposal names the company you contract with.

FAQ

Questions about how we work

Do you use AI to write code?

Yes, where it helps. The AI tools work inside your project’s code with limited access, and an engineer reads and tests every change.

What happens if I want to change something?

We work out what the change adds to the work, the time and the price, and send that to you in writing. We start once you approve it.

Does a small project need every step?

Yes, but each step gets smaller. A small fix still gets a short brief, a review, a test and a careful go-live.

Can you work inside our tools and our way of doing things?

Yes. We can work in your code storage, your task tracker and your review steps. Where your rules are stricter than ours, yours apply.

Where is your team?

In Pakistan. Our engineering and project work is managed from there for clients in other countries. Your project documents name the company you contract with.

  1. 1Describe the challenge
  2. 2We ask the right questions
  3. 3You get a clear next step

Want to see how this would work on your project?

Tell us about your project. Within one business day we’ll show you how these six steps would apply to it.

  • The first conversation is free
  • NDA before you share anything
  • A reply within one business day