01
The Challenge
Lightbox VC — one of the region's most active venture capital firms with $400M+ in assets under management and 32+ portfolio companies including three unicorns — was operating with a digital presence that couldn't keep pace with the fund's ambitions.
Every portfolio update, team change, or announcement required going back to engineering. Publishing was slow. Operational agility was constrained. For an investor-facing organisation where speed and credibility directly shape perception, this wasn't a minor inconvenience — it was a strategic liability.
The brief: deliver a polished, investor-grade digital platform with a custom admin system that the internal team could own and operate — without touching code.
02
My Role & Scope
I served as the single point of accountability across business, design, development, and QA — end to end. There was no fragmented ownership. Decisions moved through me, and delivery was my responsibility.
This meant translating the fund's brand positioning and investor communication needs into a precise digital architecture — then coordinating design and development execution to bring it to life on deadline and to spec.
It also meant building governance structures that would hold after handover: documentation, admin workflows, and a system architecture the team could confidently extend as the portfolio grew.
03
What We Built
The core deliverable was a dual-layer platform: an investor-facing public website and a custom admin panel sitting behind it.
The public site was built to communicate fund identity, portfolio depth, and team credibility to LPs, founders, and the broader ecosystem. Content architecture was designed around how investors actually evaluate a fund — thesis clarity, portfolio track record, and team signal.
The admin panel gave internal stakeholders direct control over portfolio listings, team profiles, news posts, and announcement publishing — without involving a developer. The system was built for non-technical users, with structured content types and clear publish/edit workflows.
The result: a team that could push a portfolio update or announce a new investment within minutes, not days.
04
Execution Approach
Projects at this level fail at handoffs — between brief and design, design and development, development and launch. I structured the engagement to eliminate those gaps.
Requirements were documented with enough precision that design decisions had rationale, and development had no ambiguity to fill with assumptions. Review cycles were structured so feedback was actionable, not open-ended. QA was conducted against a defined acceptance checklist, not intuition.
The entire project — from kick-off to live deployment — ran from April to July 2025, a timeline that required tight coordination without sacrificing the quality standard a firm of this calibre expects.
05
Outcomes
The platform went live on schedule with zero critical post-launch issues. Engineering dependency for content operations dropped by 70% — the internal team took full ownership of the admin system from day one.
Portfolio publishing, announcement updates, and team page management shifted from multi-day engineering requests to same-day internal execution. Operational agility improved materially, and the fund's digital presence now reflects the quality and credibility of the portfolio it represents.