Technical leadership · Build
Hands-on technical leadership for your product and team
A Technical Lead who owns your architecture, roadmap and hiring once the product outgrows the person who started it. We led a team of twelve for four years.
EngagementHourly · remote
Hours9–18 CET · 4 h overlap
StackArchitecture · roadmap · hiring
Proof4 case studies
The service in 4 parts
01 · Who it’s for
A company whose product has outgrown the person who started it, or a client that needs a single technical owner for the architecture, the roadmap and the team.
02 · What we’ve built
- Technical Lead on a US marketplace for four years, leading a team of twelve and owning the architecture, roadmap, hiring and client relationship. Four phases, zero outages.Case study 04 →
- Engineering standards set for each codebase and enforced in CI, and only then AI brought into the team’s daily work. The team’s throughput went up about 50%, which we estimated by comparing ticket cycle times.Case study 03 →
- Development lead on a construction company’s ERP with a team of four: ten modules in six months, now in production.Case study 16 →
- Redshift chosen for a fashion supplier’s data warehouse because the client was moving every service to AWS. That kept the warehouse in the same cloud and account as everything else, maintained by the same team.Case study 13 →
03 · How we work
01 · ROLE AND SCOPEThe role is Technical Lead or Software Architect, with a written scope that says which areas the lead owns and where they only advise.
02 · DECISION RECORDSEach architecture decision is recorded with its reason. When the team grows or the lead changes, the next person can revisit a decision instead of arguing it again from the start.
04 · Stack
Architectureroadmaphiringcode standards in CIwritten decisionsNode.jsReactAWS
Proof
Where we’ve done this before
Case study 04 · MarketplaceZero outagesTechnical Lead on a US marketplace for four years, leading a team of twelve and owning the architecture, roadmap, hiring and client relationship. Four phases, zero outages.Read the case study →Case study 03 · Platforms~50%Engineering standards set for each codebase and enforced in CI, and only then AI brought into the team’s daily work. The team’s throughput went up about 50%, which we estimated by comparing ticket cycle times.Read the case study →Case study 16 · Business systems150,000Development lead on a construction company’s ERP with a team of four: ten modules in six months, now in production.Read the case study →Case study 13 · Data15 min → 0.2 sRedshift chosen for a fashion supplier’s data warehouse because the client was moving every service to AWS. That kept the warehouse in the same cloud and account as everything else, maintained by the same team.Read the case study →
FAQ
Questions about this service
Yes. On the marketplace, the same four years as Technical Lead included designing and building an analytics layer that takes two million writes a day.
It can be part of the role. On the marketplace, hiring sat alongside the architecture, the roadmap and the client relationship.
Whatever is losing money or data. On the marketplace that meant two months of stabilization before any rewrite: adding a firewall, closing the security holes we inherited and indexing the twenty slowest queries.
We would share code sooner. There were nineteen repositories and no shared package, so one queue helper was copied into seven of them. A shared internal package should exist by the fifth service.
Next step
Describe the problem and we’ll come back with three options.
The first call takes 30 minutes, and you’re under no obligation.