---
id: KB-PS-019
url: https://app.codecontract.io/help/getting-started/how-much-time-this-really-takes
idioma: en
categoria: primeros-pasos
subcategoria: recursos
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PS-013, KB-PS-015, KB-PS-016]
citadoPor: [KB-PS-009]
---

# How much time this really takes

_The question nobody asks in the demo and the one that decides whether this sticks. The work does not vanish: it moves._

**Responde a:** how long does this take to implement · who is going to spend hours on it · we have nobody for this · how much work is it to maintain

Demos show how quickly everything gets done, and that is true. What they do not show is that at some point someone has to sit down and decide what is requested, from whom and how often — and that stretch of time exists, however you dress it up.

## Where the time goes, by phase

| Phase | What it usually costs | Who does it |
| --- | --- | --- |
| Deciding what is asked and from whom | A few hours, once | Whoever chases those documents today |
| Building the first process | Less than you would think | The same person |
| Loading what you already have | Depends how much you bring | It can be shared out |
| The first month of running in | A short stretch each day | Whoever owns it |
| From then on | Less than before you started | The team, without noticing |

> [!IMPORTANT]
> The row that decides the outcome is the first, and it is the one everyone tries to skip: **thinking through what exactly is requested is the work, building it is the formality**. If those hours are not spent at the start, they are paid in months of corrections, badly framed requests and outsiders asking what you actually want. It is not implementation time: it is time spent ordering what you were already doing from memory.

## What stops happening

**En corto**

- Chasing by phone what someone should have sent a fortnight ago.
- Hunting for a document that lived in someone else's inbox.
- Rebuilding a whole folder before every audit.
- And explaining for the umpteenth time which papers are needed.

> [!WARNING]
> Something worth saying that the numbers do not show: **the saving does not appear where the work was**. Whoever was chasing stops chasing, but whoever builds the processes spends time up front, and they are not always the same person. If the one who gains time and the one who invests it differ, say so out loud at the start — otherwise the person carrying the initial load ends up feeling this only added work for them.

## A realistic split for a small company

1. **One unhurried afternoon for the first process** — Better a whole afternoon than six twenty-minute slots.
2. **Fifteen minutes a day for the first two weeks** — Look at what arrives and fix what does not fit.
3. **Half an hour a month tidying up** — What is stalled, what has no owner, what is about to expire.
4. **And a longer review once a year** — Permissions, templates and whatever is no longer used.

> [!NOTE]
> If nobody can spare that first afternoon, it is better to start with a smaller process than to start five half-built. What sinks a rollout is not going slowly: it is leaving three things half-set-up and nobody knowing which is live.

**Do we need to hire someone?**

In a small company, no. Someone needs to have the time.

**What if nobody has time right now?**

Start with what is already costing you hours: it pays for itself.

**How long before it shows?**

The first weeks cost; the change shows on the second cycle.

## Ejemplos

**A company spreads the start across odd moments and three weeks in nobody knows what is set up.**

- Devotes a whole afternoon to one process and leaves it running

→ The second process takes an hour, because the hard decisions were already made.

**Effort is estimated from training rather than from designing the process.**

- Counts the time spent deciding what is requested and from whom

→ The estimate includes the part that actually costs.

**Nobody accounts for the time spent waiting on suppliers.**

- Launches what depends on outsiders early

→ The wait is not added at the end of the schedule.

**The rollout happens in odd moments between meetings.**

- Blocks a whole afternoon for the first process

→ Decisions are taken once instead of picked up five times.

**Maintenance is expected to be zero once it is set up.**

- Reserves time monthly to review templates and expiries

→ The system is still true six months later.

**Time spent is compared against zero rather than against the previous way.**

- Measures how long closing a file used to take

→ The balance is struck against a real cost already being paid.