The Tize guide
How a website is born and lives.
The principles we work with, illustrated live. No smoke: every diagram below is real code in motion.
Contents
20 chapters
Twenty chapters, one idea each.
Chapter 01
Everything leaves a trace.
In one sentence
An honest website is born from a single source of truth: one repository, one team, one truth.
Before a single pixel: the ground rules. Where the project lives and how it stays honest.
One single source
Every project lives in one place: one repository, one truth. Nothing lives in ten places at once — that is how inconsistencies are born.
Everything is derived
Design, code and metrics all come from that same origin. When the source changes, everything changes with it — coherent by construction, not by discipline.
Traceable
Every change is recorded: what, when and why. A website you can audit is a website you can trust — today and in two years.
Chapter 02
Made to iterate.
In one sentence
Iterating without fear needs safe branches: test, compare and pick the best.
Iterate without fear: branch, test and choose. We copy the state you have, try the change on top of it and keep what works — nothing that already works breaks.
Chapter 03
Next to your business.
In one sentence
A website doesn't live alone: it connects with your real business, data and tools.
Your website connected to your real operation: the signals your business already produces feed the interface, instead of living in a separate dashboard nobody opens.
Chapter 04
Measured, not promised.
In one sentence
What gets measured improves — what gets promised without measuring gets forgotten.
What gets measured improves. The meter below is live: the needle rises with every event and the counter keeps the score — no promises, readings.
Chapter 05
The config.
In one sentence
If your website is described in clear files, anyone can review, repeat and improve it.
Your website described in clear files: what you see can be reviewed, repeated and improved without magic.
Chapter 06
Review before applying.
In one sentence
Nothing reaches production without someone having reviewed it first.
The change is prepared, shown and confirmed before it is applied: what will change, what stays the same and what happens if we accept it. Reviewing is cheap; fixing in production is not.
Chapter 07
What arrives late, arrives.
In one sentence
Every event is logged whole — what, when and who — and anything late is logged with its real time.
One record per event: id, timestamp and context. If data arrives late it is logged with the time it happened and the time it arrived: nothing is lost and nothing is rewritten in silence.
Chapter 08
Simple parts, solid whole.
In one sentence
Everything you see comes from simple, ordered, repeatable parts.
Data comes in raw, groups into small buckets and seals when the period ends. With short, predictable rules the whole holds up: any figure can be rebuilt from scratch.
Chapter 09
In tiers, with clarity.
In one sentence
Scope and price are explained in tiers: you know what each one includes before deciding.
One tier, a bigger one, a complete one: each level says what you get and what it costs, with no small print. And if something changes during the project, the change is visible and approved — it never just shows up on the invoice.
Chapter 10
Native to agentic workflows.
In one sentence
Agents propose and prepare; the review and the final yes stay human.
Assistants and agents work on your project: they measure, compare and leave changes ready on a branch. Control doesn't move — review, approval and a name on every merge. We automate the paperwork, not the responsibility.
Chapter 11
Local-first checks.
In one sentence
It is tested in your environment first, with no risk; only then it goes to production.
Rules and calculations run locally while you work: the answer lands in milliseconds, with no round trips. What works on your machine is what ships, and what changes out there syncs in the background without holding you up.
Chapter 12
The balance, in plain sight.
In one sentence
What you hired and what you used are always visible; you don't discover them at the end.
The counter below is live: every event draws down and every top-up is logged with its date. A project never runs out of air without warning, and nobody gets a surprise at closing time.
Chapter 13
Access and permissions, clear.
In one sentence
From day one you can see who can do what, and up to where.
One gate, a set of keys and a limit per person, team or service: access switches on and off on purpose, and what is off is visible too. Nobody wanders where they shouldn't.
Chapter 14
Every figure, reconciled.
In one sentence
The numbers add up in the end, and there is always a floor that doesn't get crossed.
What is computed locally is checked against what is stored, and differences get corrected, not covered up. And over every price or deadline promise there is a minimum in writing: quality is not negotiable.
Chapter 15
Nested identities.
In one sentence
One brand with several projects: each account on its own and the total added up.
Every project, team and person has their own identity and usage; access flows down from the top and consumption rolls up to the root. You can see each part and see the total, without mixing accounts.
Chapter 16
What each one uses.
In one sentence
Usage and cost are read per identity: each part, with its figure next to it.
Usage by team, person and service in the same table, next to what each one brings. Deciding where to invest stops being a hunch and becomes a reading.
Chapter 17
Levers and decisions.
In one sentence
Every decision carries its consequences beside it: what changes, what is gained and what is at risk.
Changing a price or widening the scope has consequences, and here they are seen together, side by side: what changes, what is gained and what is at risk. The full comparison draws itself in front of you, so decisions are made by looking — not from memory.
Chapter 18
What is granted and what runs out.
In one sentence
What is granted has a date, and what runs out warns you in time.
Every reserved block shows when it expires and what is left; if the balance crosses a limit an alert fires and you decide what happens next. Warnings arrive with room to spare, not when nothing is left.
Chapter 19
With the tools you already use.
In one sentence
Your project connects with what you already use — no changing habits, no lock-in.
Every call to a provider goes through where you decide, and the charge lands on your processor and your account. The integration fits the way you work, not the other way around.
Chapter 20
Money, no grey areas.
In one sentence
Every charge reaches your bank with its tax already checked, on the same line.
What your client pays, the tax that applies and what lands in your account, one after the other. The boring part is sorted before the invoice reaches you.
Start here