Spera began as an ambitious attempt to rethink how independent professionals run their businesses. Freelancers, contractors, and small teams were increasingly operating like companies, but the tools available to them were fragmented and mismatched. Project management lived in one place, invoicing in another, payments somewhere else entirely. The result was friction, lost time, and unnecessary cognitive load around getting paid.
I joined Spera during a phase where the vision was clear, but execution required structure. My role centered on guiding the product end to end, aligning business goals with system design, and helping the team turn a broad idea into a coherent platform that could support real financial workflows across web and mobile.
The problem
Independent professionals were not struggling because they lacked tools, but because their tools were never designed to work together. Managing clients, tracking work, sending invoices, and receiving payments required stitching together multiple systems, each with its own mental model and failure points. This fragmentation introduced risk, especially when real money was involved.
The challenge was not to build another single-purpose app, but to design a platform that treated projects, clients, invoicing, and payments as connected parts of one system. The product needed to feel approachable for solo users while remaining robust enough to support growing teams and increasingly complex workflows.
The platform approach
Spera was designed as a unified system rather than a collection of features. Core objects such as clients, projects, invoices, and payments were treated as shared primitives across the platform, allowing actions in one area to naturally inform others. This reduced duplication, improved clarity, and created a foundation for long-term scalability.
From an experience standpoint, the goal was to minimize friction without oversimplifying the underlying mechanics. Users should not need to think about accounting concepts to send an invoice, but the system still needed to enforce consistency, accuracy, and traceability behind the scenes.
My focus throughout was maintaining coherence between experience and infrastructure. Product decisions were evaluated not just on usability, but on how well they held up when extended across billing cycles, reporting, and real financial transactions.
Role and execution
I worked closely with design and engineering to shape the product roadmap, define system boundaries, and guide implementation decisions. Rather than operating in isolation, I acted as a connective layer between disciplines, ensuring the product vision translated into practical, buildable solutions.
This included guiding early discovery, aligning stakeholders around priorities, and helping the team navigate tradeoffs between speed, quality, and long-term maintainability. The work required balancing ambition with realism, especially in an environment where financial trust was critical.
Outcome
Spera emerged as a cohesive platform that allowed independent professionals to manage their work and income in one place. While the product addressed a broad problem space, its success came from treating complexity as a design challenge rather than something to hide or defer.
The project reinforced an approach that has shaped much of my work since: platforms succeed when systems, experience, and business logic are designed together, not layered on top of one another after the fact.