Selected work / 03
The Vertical
One address, two operating systems. For the Grand Vertical, Voortgang designed and engineered the marketing and executive HQ that plans, approves, and reports the campaign to fill the tower — and the tenant operations platform that runs life inside it, from first service request to resolved ticket.
Grand Vertical — elevation sheet
One address.
Two operating systems.
System IMarketing & executive HQ
- Plan
- Approve
- Run
- Report
The system that plans and reports the campaign — targets, approvals, actuals, reporting.
System IITenant operations
- Request
- Assign
- En route
- Tracked
The tenant service workflow — tickets, notices, inboxes, visible states.
Grand Vertical — elevation sheet · development render · two operating systems
The engagement
A tower needs software the way it needs structure.
Selling a building is a marketing operation with a hard number at the end of the funnel: the square footage it must fill. Running one is a service operation where every request deserves a visible state. For The Vertical, we built both.
The first platform fills the tower — planning, targets and actuals, channel reporting, and executive visibility for the team marketing the Grand Vertical. The second runs it — service requests, tickets, announcements, and inboxes for the people who move in. Two builds, one discipline: make the plan explicit, record what actually happened, and let the difference be seen.
- DrawnThe Grand Vertical — an architectural elevation, and the development render it became.
- PlannedSquare-footage targets split across channels; brand enters the plan, the CMO approves it.
- RunActuals, task states, and live inboxes report the campaign as it actually happens.
- ServedTenant requests arrive through a guided wizard and come back as tickets with visible states.
Platform I — the marketing & executive HQ
The engine that fills the building.
An internal HQ for the marketing team and the executive office: brand managers enter the plan, sales ops records the actuals — with an audit trail — and the CMO approves, overrides, and reads the whole picture. Channel and monthly reports, a task conveyor with real approval states, live inboxes, and an AI desk that answers questions about the work. Interfaces shown with synthetic data.
Planned backwards from square footage.
- Target sqft
- Deals
- Meetings done
- Meetings scheduled
- Qualified
- Leads
Every channel's plan is computed backwards from the square footage it must sell: the target implies deals, deals imply meetings, meetings imply qualified leads. Three channels — digital, inbound, activations — each own a contribution of the target.
Orchestrated, end to end.
- PlanBrand
- ApproveCMO
- RunMeta campaigns · MCP-orchestrated
- MeasureSales Ops actuals
- ReadIntelligence Desk
Campaign execution on Meta is orchestrated through MCP-assisted automation, feeding the same reporting spine the team already answers to — plan in, actuals back, one ledger.
The handover
From campaign to service.
The two platforms share one discipline. The HQ gives the marketing plan an explicit state — entered, approved, reported against. The tenant platform gives every service request the same — submitted, assigned, en route. Different rooms, one rule: record the work, and let its state be seen.
Platform II — tenant operations
The building, answering back.
For tenant operations, the relationship inverts: tenants ask, and the building answers. A guided request wizard, tracked tickets with visible states, building announcements, an inbox, feedback, resources, and a contact directory — in a tenant view and an admin view that read from the same record. Interfaces shown with synthetic data.
Resources and contacts.
Alongside the request flow, the platform carries a knowledge base with FAQs, a document library, and a contact directory grouped by department — property management, accounts, maintenance.
Notices, with priority.
Building announcements carry a category, a date, and a high, medium, or low priority — part of the same tenant surface.
The system
Two platforms, one discipline.
A few of the decisions that shaped both builds — open one to see why it was made.
Roles are the workflowBrand plans · Sales Ops records · CMO approves
The workflow lives in the database, not in etiquette: row-level security and workflow guards decide who can enter a plan, who can record actuals, and who can approve — and changes to actuals carry an audit log. The org chart is enforced, not implied.
Reporting reconciles plan against realityTargets and actuals, side by side
Every channel report and monthly snapshot puts the plan next to what happened, per channel, per month. The funnel is computed backwards from the square-footage target, so a miss anywhere in the chain shows up as a number, not a feeling.
The inbox is live, not polledRealtime database subscriptions
Approvals, comments, and nudges land in the marketing home the moment they happen, over realtime subscriptions to the database itself. Nobody refreshes to find out what changed.
The AI desk reads only the ledgerBounded data pack · scheduled + on demand
Intelligence Desk summaries are generated from a bounded pack of the team's own tasks and signals — blockers, priorities, risks, next actions. If data is missing, it says so. Scheduled digests for the executive office, questions on demand.
One request, two viewsThe same ticket, tenant-side and admin-side
A tenant's request and the admin's queue are the same record in different clothes. Status changes — submitted, assigned, en route — travel to both sides, so “what's happening?” never needs a phone call.
- Strategy — Voortgang
- Platform strategy, information architecture
- Design — Voortgang
- UX/UI, design systems
- Engineering — Voortgang
- Architecture, front-end & backend, Supabase integration
- Automation — Voortgang
- Meta campaign orchestration via MCP