Smart Launch Web and App Solutions

How a project runs

The steps are the same for a small website and a large app. What changes is how long each one takes.

  1. Understand the problem

    A conversation and, where useful, a visit to see the work as it is done today. We write down the problem, who is affected, and how success will be measured.

  2. Scope and quote

    A written scope that lists what is included and what is not, a fixed price or a capped estimate, and a timetable. Nothing is built before the client agrees it.

  3. Design

    Screens, data and connections are designed and reviewed with the client. For interfaces, a design system is agreed first so every screen follows the same rules.

  4. Build

    Work is delivered in small, reviewable pieces, with progress the client can see before the end of the project.

  5. Test

    Automated tests run on every change. Before release there is a security review, an accessibility check and a trial with real users where possible.

  6. Release and hand over

    The software goes live, and the client receives the source code, the documentation, the list of accounts and services it depends on, and a recovery guide.

  7. Support

    A support period is agreed in writing. After that, the client can extend it, take the software in-house, or hire another developer.

Engineering practices applied to every project

  • Strict type checking in TypeScript from the first line of code, because adding it later is far harder.
  • Automated checks on every change: code quality, known vulnerable dependencies, and tests, before anything is released.
  • Infrastructure defined as code and reviewed like any other change, so environments can be rebuilt and audited.
  • Important decisions recorded in short written notes that explain what was chosen, what was rejected and why.
  • A design system for interfaces, so appearance and accessibility are consistent.
  • Secrets such as passwords and keys kept in a secrets manager and never in source code.

Privacy by design

Each project begins with the question of which personal information is genuinely needed. We collect the minimum, define how long it is kept, and build access, correction, export and deletion into the software as real features. High-risk processing gets a written impact assessment before it starts. Our privacy policy and security page describe the practices in more detail.

Working relationship

We communicate in writing so that decisions can be found later. Response times and support hours are set in each statement of work. General questions are answered through [email protected] and support requests through [email protected].