---
id: KB-PS-003
url: https://app.codecontract.io/help/getting-started/your-first-week
idioma: en
categoria: primeros-pasos
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-PS-001, KB-ET-001]
citadoPor: [KB-PS-006, KB-ET-009, KB-PS-007, KB-PS-010, KB-PS-011, KB-PS-013, KB-PS-005]
---

# Your first week

_What to do in the first days so the platform actually earns its keep, in order._

**Responde a:** where do i start with code contract · what do i do on day one · how do i get the platform running · quick start guide

The commonest mistake when starting is trying to set everything up before using anything. It takes two weeks, gets abandoned at the first obstacle, and nothing has been gained. This order does the opposite: something working on day one.

**En corto**

- One real process end to end beats ten half-built.
- Invite the team when there is something to show them.
- What you do not use in week one, you probably do not need.

## Day 1 — a real case

Take something that is on your desk today: a supplier to chase for paperwork, a contract to sign. Do it end to end on the platform, even if it is slower than email that first time. It is the only thing that really teaches how the pieces fit.

## Day 2 — turn it into a template

Save what you just did as a process. From then on the second case takes two minutes.

## Days 3 and 4 — the team

Now invite people. Bring them in with something that already works in front of them, not an empty screen. Give each of them what they need and nothing more: someone who only looks does not need to be able to delete.

## Day 5 — what slips through

Look at which of your own documents expire and set the dates. That is what turns the platform into something that warns you, rather than a filing cabinet you have to go and check.

> [!NOTE]
> If by the end of the week you have one repeatable process and three people using it, you are on track. If you have twelve processes and nobody inside, go back to day one.

**How long until it is running?**

One real case, the first afternoon. The whole team, a week.

**Do I need IT help?**

Not to start. Only to connect email to your own domain, and that can wait.

**What if I set something up wrong?**

Everything can be changed later. Nothing from day one is irreversible.

## Ejemplos

**A twelve-person company starts on a Monday.**

- Monday: chases a real supplier for paperwork
- Tuesday: saves it as a process
- Thursday: three colleagues join
- Friday: sets expiry dates on their insurance

→ The following Monday the second supplier takes two minutes and nobody needed training.

**A company spends the first week configuring and asks nobody for anything.**

- Picks a real process that already hurts and launches it on day one
- Adjusts the configuration around whatever comes up

→ Configuration is decided from real cases rather than assumptions.

**The whole team is invited on day one and nobody knows what to do.**

- One person starts with a process of their own
- The others come in once there is something to show them

→ Whoever joins finds something working rather than an empty tool.

**On day three the same thing must be requested from another supplier and it is rebuilt from scratch.**

- Saves the first process as a template
- Launches the second supplier from it

→ The second request takes two minutes instead of half an hour.

**Nobody knows whether the supplier received the request.**

- Checks the status of each request sent
- Lets the reminders go out on their own

→ You stop emailing to ask whether it arrived.

**The first week ends with nothing to show management.**

- Closes one complete file, however small
- Shows it with its trail and its dates

→ The decision to continue is taken on something done rather than a promise.