The decisions made in the first 90 days

Early-stage companies routinely defer the CTO hire. The logic is understandable: a full-time senior technology leader is expensive, and in the early months the founding team is usually close enough to the engineering work to manage without one. The cost of that deferral compounds quietly. Architecture decisions get made in a hurry. Technical debt accumulates without anyone tracking it strategically. Investors start asking questions the founders cannot answer with confidence. By the time the need feels urgent, the organisation has often already made several decisions that are expensive to reverse.

A product instinct is not the same as an architecture instinct. Most early-stage companies discover this distinction too late - once the wrong stack choice has compounded into an 18-month migration, once the data model cannot support the feature the investor is asking about, once the first senior engineer hire arrives and immediately identifies foundational problems that need rebuilding. Technical co-founding engagement addresses exactly this: the decisions made in the first 90 days that determine the cost structure and agility of the business for the next three years.

This is not a consulting relationship where a senior advisor attends weekly calls. It is a hands-on, embedded engagement that holds real accountability for technology outcomes - attending leadership discussions, owning the technical roadmap, and maintaining a direct relationship with the founding team until a permanent technical leader is in place.

What the engagement covers

Architecture and stack decisions

Auth, infrastructure design, data model, deployment pipeline, and service boundaries are not secondary concerns to be revisited after the MVP. Gradion maps the specific trade-offs against the company’s product timeline, funding horizon, and hiring market - not imposing a preferred stack, but making decisions with enough context that they do not need to be revisited. In 2026, that includes AI tooling decisions: which development tools the team adopts, how they are integrated into the workflow, and what that means for the hiring profile of the first engineers.

Investor-facing technical credibility

Pre-seed and seed investors increasingly bring technical advisors into due diligence. Architecture documentation, scalability narrative, infrastructure cost modelling, and a coherent answer to how the system holds at 10x current load are not late-stage concerns. Gradion prepares that story as a byproduct of the technical work, not as a separate documentation exercise. The result is a technical narrative that reflects production reality - the only kind that survives investor scrutiny.

Build versus buy decisions

Where to use managed services, open-source tooling, and third-party APIs versus where to build proprietary capability shapes both the company’s competitive positioning and its cost structure. Gradion maps this with a pragmatic lens: proprietary code is a liability as well as an asset. The goal is to identify where building is genuinely necessary for differentiation and where it is an expensive habit that managed tooling can replace.

First engineering hire criteria

Defining what the first engineering hire needs to be able to do, before the company is ready to hire, is one of the highest-leverage decisions in early-stage company building. Gradion works with founders to scope the role based on the architecture already in place, the roadmap ahead, and the founder’s own technical capability. In an AI-augmented environment, that profile includes AI tooling fluency as a primary criterion, not an afterthought.

When the engagement ends

Technical co-founding engagement is designed to close. The goal is to establish the architecture, team foundations, and technical leadership capability so the company can appoint a permanent CTO or promote an internal engineering lead. The handoff is explicit: documented architecture, defined engineering standards, a hiring brief for the permanent hire, and a structured transition period.

Proof in production

LemonSwan came to Gradion in 2017 as a single person with a concept and no engineering team. Rather than hire a CTO into a company that did not yet exist as an organisation, Gradion embedded a senior technical partner into the founding team, built the platform from the ground up, and stayed through the full arc from concept to operational independence. That developer was eventually relocated from Asia to Germany and became LemonSwan’s CTO. By 2024 the company had reached an estimated €8 million in annual revenue and established itself as a trusted brand in the German and Central European dating market - built on architecture and leadership decisions made in the earliest phase, when a full-time hire would have been premature and a purely technical contractor would have been insufficient.

“From the very beginning, working with Gradion felt like a true partnership. Gradion didn’t just bring strong technical expertise; they consistently went the extra mile, thought with us, and adapted when things got tough.”

Paul Uhlig, Managing Director, LemonSwan

CTA

Describe the company stage, the technical problem, and the co-founder gap. We scope these engagements in two weeks.