Ideas in.Productsout.

Yes – I take on a small number of projects alongside my CTO role at Upwex, which keeps the bar high for what I commit to. The best first step is a short email describing what you're building.

Three formats: project-based delivery with a written scope, a fractional tech-lead role (part-time, ongoing), or a focused architecture audit. Long-term contracts are possible when the product is interesting.

Central European time (Portugal). That gives full overlap with European teams and comfortable morning overlap with US East Coast. Async-first communication works best either way.

Yes – legacy rescue is a specialty. I've migrated large AngularJS platforms to modern Angular and untangled codebases past 100k lines. The process starts with a read-only audit week, then a prioritized plan before any rewrite talk.

It depends on the team you'll hire, not fashion. My defaults: Next.js or React for most web products, Angular for large enterprise teams that value convention, React Native when web and mobile share a domain, NestJS + MongoDB on the backend.

Both. I can ship a product end-to-end alone – architecture to store review – or embed into your existing team as a lead: reviews, mentoring, hiring loops and standards included.

Email sinclar96@gmail.com with two paragraphs: what you're building and what's blocking you. You'll get an honest reply – sometimes that's 'you don't need me yet' – and if it fits, a call and a written scope within a week.