Management, brand & direction
Management, brand and direction
Most of what we build goes better when someone has first decided what the business is, how it is organised and what matters most this quarter. That is this sheet.
Built and running at Lawang Estate, a property developer selling villas and land. The figures below are theirs.
01 · What it is
This is the work that crosses both axes. Before a CRM there is a sales process; before a campaign there is a brand; before an internal suite there is an organisation that decides who does what. When those are unclear, the software ends up making the decision by accident.
More detail
We sit beside the owner and do three things. Brand: identity, voice and the rules that keep it consistent across the website, the documents and the accounts. Organisation: who owns each process and each piece of data, written down. Direction: what to build or fix first, chosen by what costs the most today.
Everything we decide is written down with its reason and its date, so the next person — or the next us — can tell why it was decided and whether it still holds. A decision that only lives in a meeting is gone the week after.
02 · Seen working
Lawang Estate — from brand to operations
Sample data in the shape of the real tool. No names, no amounts.
What a decision log looks like: what was decided, by whom, and whether it is applied yet.
| Date | Area | Decision | By | Status |
|---|---|---|---|---|
| W39 | Sales | Who may edit a buyer record | Owner | Applied |
| W39 | Brand | Palette for a new project | Owner | Applied |
| W38 | Finance | How a commission is approved | Owner | Applied |
| W37 | Operations | One registration point per person | Owner | Applied |
| — | Legal | Licence for a typeface | Owner | Waiting |
IN PRODUCTION
For the developer we built the brand system — identity, palette, voice — and the organisation the software enforces: who owns each process, which role sees what, how the sales teams are structured. Every owner decision is logged with its reason and date, and anything waiting on someone sits in a single book with an owner and an age.
MODULES · 8
- Brand identity
- Voice
- Organisation and roles
- Sales teams
- Priorities
- Decision log
- Pending book, with owner and age
- Regular review
03 · How it flows
- 01ListenWhat the owner needs and what hurts.
- 02DecideWith the data on the table.
- 03WriteThe decision, its reason, its date.
- 04BuildThe software enforces it.
- 05ReviewAgainst what we said we would do.
04 · What’s included
| # | Component | What it means |
|---|---|---|
| 01 | Brand identity | Name, logo, palette, type and voice, with the rules that keep them consistent. |
| 02 | Organisation | Who owns each process and each piece of data. |
| 03 | Priorities | What to build or fix first, ranked by what it costs to leave it. |
| 04 | Pricing structure | How the offer is presented — never the number, which is yours. |
| 05 | Decision log | Each decision written with its reason and its date. |
| 06 | Review | A regular look at the numbers against what we said we would do. |
| 07 | Handover | Everything documented so it does not depend on us. |
05 · Questions
Is this consulting?
Do you set our prices?
Can we hire only the brand work?
How often do we meet?
What does it cost?
Start a project
Have something worth building well?
Tell us what you are working on. We reply in English or Spanish, usually within a day.