Fractional CTO · tech + product + team pivot · 2023
Side.xyz — fractional CTO brought in to pivot tech, product, and team.
Contracted as fractional CTO to pivot Side across three dimensions at once: the technology stack, the product positioning, and the team. Shipped the pivot in 2023, with the platform going on to evolve into what today runs as an AI agent platform at side.xyz.
The shape
Fractional CTO
Engagement shape
3
Dimensions pivoted · tech · product · team
2023
Pivot shipped
Handoff
Team left owning the direction
The problem
A pivot that only touches the code is a rewrite. A pivot that only touches the pitch is a rebrand. The Side engagement needed the real thing — tech, product, and team moving together, in a single sequence, without losing the people or the momentum that already existed.
Every multi-axis pivot has the same trap: fix one dimension in isolation and the other two break around it. Rewrite the stack before the product is clear and you ship the same confusion on new rails. Reframe the product before the team is aligned and the roadmap becomes fiction. Change the team before either is settled and you lose the institutional memory.
The brief was blunt: come in as fractional CTO, own the three-way pivot, leave the team with a stack, a story, and a structure they can run themselves.
What I did
Four layers of a three-axis pivot.
Tech pivot — retire what doesn't carry, pick foundations for the next three years
Audited the stack against where the product was actually going, not where the repo had accreted to. Retired the parts that were legacy from the previous direction. Chose foundations that would survive whatever came next — language, framework, infra, data model — and migrated incrementally so the team shipped through the pivot, not around it.
Product pivot — reframe what Side actually is
The product story had been shaped by the prior direction. Worked with the founders to re-articulate what the platform was for, what a win looked like for a user, and what specifically we were not going to build. A shorter deck, a tighter roadmap, and a home page that described the product the team was actually shipping.
Team pivot — right people, right work, clear seams
A pivot always shifts who carries what. Reviewed the org against the new roadmap — what roles were needed, which existing strengths mapped, which gaps needed hiring. Clarified reporting lines and decision rights so that once I rolled off, the team knew who owned what without me in the loop.
Handoff — leave it runnable without me
A fractional engagement fails if it creates a dependency on the fractional. Documented architecture decisions, wrote the scope and the why behind each tech choice, and set up the review cadence for the team to keep the pivot honest after handoff. The work shipped because of the team, not because I stayed.
What transferred
Lessons that reshape every fractional engagement since.
- Pivots are coupled problems. Tech, product, and team move together or not at all — isolating any one of them produces a prettier version of the old confusion.
- Fractional CTO isn't a lighter full-time CTO; it's a different shape of engagement. You're paid to ship the transition, not to run the operation that comes after.
- Name what you're not going to build, loudly. A pivot that doesn't delete anything is a rebrand wearing a Git branch.
- The best handover is the one where the team forgets you were there after three months. That's not ego damage — it's the work landing cleanly.
Engagement
- Fractional CTO engagement · 2023
- Technical architecture review + rebuild
- Product positioning + roadmap scoping
- Org design + hiring reviews
- Platform: https://side.xyz
Free download · 6 pages · PDF
The first 90 days of a Fractional CTO.
What gets audited, decided, and shipped in the first three months of an embedded engagement. Week by week, including the uncomfortable conversations most founders avoid.
No spam. You also get the Sunday note — unsubscribe in one click.
Keep reading