Name
gestión — one control centre for a studio that was running on three spreadsheets
A management platform for an interior design and decoration studio. Full-stack product design and engineering.
Description
The studio's projects were run out of spreadsheets: one for internal cost control, one sent to suppliers for pricing, one shown to the client — the same line items, maintained three times, drifting apart a little more with every renovation.
Gestión replaces all three with one control centre built around how the studio actually works. A project holds rooms; rooms hold elements — windows, wardrobes, custom carpentry — each with a quantity, a unit and a trade. Progress is worked out from the job itself rather than typed in by hand, so it cannot quietly stop matching reality. The studio runs everything from an internal panel; clients get their own space to follow their project.
Status
19 percent complete: one of eight sub-projects in production, one in progress.
8 sub-projects · 1 in production · 1 in progress
The first sub-project — the studio panel that runs clients, projects, rooms, elements, phases and photography — is delivered and in production. The client portal is in its first cycle. Six more follow: catalog, budgeting, purchasing, site tracking, approvals and documents.
███ delivered ███ in progress ░░░ planned
How it is built
Each of the eight sub-projects gets a written design before any of it is built. That is deliberate: the studio's process is the hard part, not the software. Four decisions worth naming.
- templates are copied, not linked
- Creating a project copies the blocks of work it will go through. Editing the template afterwards never rewrites a running or finished job, so the record of how a project was actually run stays intact.
- switching work off is always reversible
- Studios turn off blocks that do not apply to a job. Doing so changes nothing underneath, so turning it back on restores exactly the previous state, statuses and all. The simpler alternative would have been impossible to undo.
- progress is worked out, never stored
- It is counted fresh each time it is shown, so it cannot go stale. Whether a project is paused or cancelled stays a human decision, not something guessed from a count.
- backups are verified, not assumed
- A copy is taken nightly and kept offsite. Weekly, the newest one is restored into a throwaway database and its contents counted. An untested backup is a guess.