Skip to content
Zimcrest Technologies — home
Chat on WhatsAppStart your build

Web development

Fast, accessible web products that hold up on a 3G connection.

Start your build

What's included

The work, and what you receive

Each capability names an artefact you end up owning, not an activity we perform.

Our approach

How this runs, and roughly when

Durations are bands, not promises. We revise them in the open when the work argues otherwise.

  1. 1

    Set the budgets

    2–4 days

    Timing and byte budgets agreed before the first component, so they shape decisions rather than judging them.

    • Performance budgets
    • Target device and network profile
  2. 2

    Build in increments

    8–20 weeks

    Working software every two weeks in your repository, with tests and CI from the first commit.

    • Fortnightly increments
    • CI pipeline
    • Test suite
  3. 3

    Harden

    1–2 weeks

    Load behaviour, error paths and the degraded experience, checked under the conditions we agreed.

    • Load test results
    • Degradation report
  4. 4

    Hand over

    1 week

    Runbooks, monitoring and a named engineer for the agreed support window.

    • Runbooks
    • Monitoring
    • Support window

Tools we use

Boring, well-supported, and replaceable

We tell you when something newer is worth its risk, and when it is not.

Related work

Where we have done this

Questions

Asked often enough to answer here

Yes, from week one. You own the code throughout, and there is no handover moment where it changes hands.

CI fails and we deal with it before merge. If a budget turns out to be unachievable we say so and renegotiate it in the open, with the measurement.

Core reading and navigation, yes, wherever the feature allows. We will tell you which parts genuinely need it.

Working against a constraint?

Tell us what it is. We will tell you what we would build, what we would not, and what it would take.

Start your build