Saltar al contenido
BLOKIS
EN ES

Process 5 phases · 1 chain of decisions

We work as your
internal team.

Every phase exists to bring uncertainty down. If a stage produces no evidence, it does not move on. If it cannot be operated, it does not get designed. If it cannot be measured, it does not get promised.

phases with their own deliverable
5
visible owner per phase
1
surprises on the invoice
0
decisions written down
100%

The chain

From diagnosis to operation, with no gaps.

Same team, same log, same portal. What comes in as a problem leaves as a documented system.

  1. Phase 01 Diagnosis 1 week

    We find the real problem

    We review the business, the users, the data, the stack and the constraints. The result is a scope with the risks written down.

    Deliverable
    scope.md + risk map
    Exit condition
    Do we know what hurts and what it costs to fix?

    No scope, no price.

  2. Phase 02 Design 1–2 weeks

    We map the route before the code

    Flows, architecture, critical states and success criteria. Nothing starts without knowing how it will be operated.

    Deliverable
    technical brief + prototype
    Exit condition
    Can what we just drew actually be operated?

    If it cannot be operated, it does not get designed.

  3. Phase 03 Build 2-week sprints

    We build in short deliveries

    One- or two-week sprints with real demos, reviewable PRs and decisions written down.

    Deliverable
    release candidate
    Exit condition
    Is there something working you can touch today?

    A demo beats a document.

  4. Phase 04 Deploy Release window

    We launch with a safety net

    CI/CD, variables, backups, monitoring and rollback. Production is not the place to improvise.

    Deliverable
    runbook + observability
    Exit condition
    Can we roll back within a minute?

    Production is not improvised.

  5. Phase 05 Operate Monthly, ongoing

    We stay to operate it

    Incidents, improvements, hosting, support and technical debt kept in check. Your software stays alive after launch.

    Deliverable
    portal + weekly pulse
    Exit condition
    Is somebody watching this when it breaks?

    Software lives on after the deploy.

Where you notice it

The difference is not the code.

Almost nobody hires a process. People hire to stop living in the left-hand column.

  1. The price comes before the scope. The scope defines the price.
  2. The demo is a PDF with screenshots. The demo is touched in the browser.
  3. Production is the first real environment. Production is rehearsed before it exists.
  4. Nobody knows who touches what. Every phase has an owner with a name.
diagnostico.blokis

How we come in

We start by diagnosing, not by quoting.

The first conversation is free and produces something concrete: a map of your problem, the visible risks and a first cut of the scope. Only then do we talk about price.

Book a diagnosis See the catalogue