Skip to content

How we work

A process you can hold us to

Five phases, each with named deliverables and a decision point before the next begins. You always know where the project stands, what you have received, and what happens next.

Sors Technology delivers projects in five phases — discovery, design, build, launch and support. Each phase ends with named deliverables and an explicit go/no-go decision, so clients control scope and budget at every step rather than discovering them at the end.

  1. 01

    Discovery

    1–3 weeks

    We map how your business actually works: processes, systems, data and the workarounds nobody documented. Discovery ends with a written assessment you own — precise enough to take to a competitive tender if you choose to.

    Deliverables

    • Process and systems map
    • Problem statement with measurable goals
    • Recommended approach with alternatives considered
    • Scope, timeline and budget range
  2. 02

    Design

    2–4 weeks

    The solution on paper before it exists in code: system architecture, screen designs, data model, integration contracts and the migration plan. Design turns the discovery assessment into something an engineer can build and a stakeholder can veto.

    Deliverables

    • Functional specification
    • Wireframes or clickable prototype
    • Architecture and integration plan
    • Fixed quote for the build phase
  3. 03

    Build

    4 weeks – 6 months, scope-dependent

    Configuration and engineering in two-week increments, each ending with working software demonstrated on a staging environment you can open yourself. Code review, automated tests and documentation happen during the build, not after it.

    Deliverables

    • Working increments every two weeks
    • Staging environment with your real data
    • Test coverage and code review records
    • Progress reports in plain language
  4. 04

    Launch

    1–3 weeks

    Cut-over is planned like the operational event it is: data migration rehearsed, staff trained per role, rollback defined, and timing chosen around your business calendar — not ours.

    Deliverables

    • Rehearsed data migration
    • Role-based training with written procedures
    • Cut-over and rollback plan
    • Hypercare: daily support in the first weeks
  5. 05

    Support & improvement

    Ongoing

    After the warranty period, a support agreement with defined response times keeps the system patched, monitored and improving. Quarterly reviews turn real usage into a prioritised improvement list — small continuous gains instead of a rebuild in five years.

    Deliverables

    • Warranty period with defects fixed at our cost
    • Support agreement with response times
    • Monitoring, backups and patch management
    • Quarterly review with improvement backlog

Rules we work by

Deliverables, not activity

Every phase produces artefacts you keep — documents, designs, code, credentials — whether or not we continue together.

Decisions at the checkpoints

Budget and scope are controlled where they can actually be controlled: between phases and between increments.

Bad news travels fastest

If something slips or a risk appears, you hear it from us immediately, with options — never in a status report three weeks later.

Your ownership by default

Accounts, code, data and documentation live in your name from the first week. Leaving us must always be possible; that is what keeps us good.

Frequently asked questions

Start with discovery

The first phase is deliberately small: a written assessment of your systems, a recommended approach, and a budget range — yours to keep whatever you decide next.