Skip to content
AP

SH.04 — SERVICE CATALOGUE

Engineering, as a service.

I take on part-time roles and contracts across the whole product — native mobile apps, the Go services behind them, the AWS they run on and the AI features on top. Based in London, working remotely or hybrid. One thing up front: I'm not looking for a full-time move. I lead product engineering at nHabit, and every engagement gets the same standards I hold there.

Open to part-time & contract
[ FIG.01 ]THE CATALOGUE

Everything a product needs to ship

SVC.01 // PRIMARY

Websites & Web Apps

From marketing sites that rank to full product platforms

High-performance websites and web applications engineered with Next.js and React — server-rendered for SEO, obsessively optimised for Core Web Vitals, and designed to convert. From brand sites with CMS-driven content to complex multi-tenant SaaS platforms with billing, auth and dashboards.

DELIVERABLES

  • Marketing & brand sites with CMS
  • SaaS platforms & customer portals
  • E-commerce & payment integration
  • Progressive web apps
  • Performance & SEO overhauls

STACK

Next.jsReactTypeScriptTailwindCSSSanityStripeOpenNext · AWS

SVC.02 // PRIMARY

Mobile Apps

Native iOS & Android, shipped to both stores

Native apps in Swift and SwiftUI, Kotlin and Jetpack Compose — the stack I used to rebuild nHabit's apps: the Android app solo with about 2,400 tests, the iOS app with one other engineer. Store releases, release automation, crash reporting and test coverage included, not bolted on. React Native when one codebase is the right call.

DELIVERABLES

  • Native iOS (Swift, SwiftUI)
  • Native Android (Kotlin, Jetpack Compose)
  • App Store & Google Play releases
  • Fastlane & CI release lanes
  • React Native when it fits

STACK

SwiftSwiftUIKotlinJetpack ComposeFastlaneSentry

SVC.03 // SECONDARY

Backend & APIs

The systems behind the screens

Go and Node.js services, REST APIs, data pipelines and AI integrations — designed with domain-driven boundaries, typed contracts and the operational discipline of someone who carries the pager for their own systems.

  • Go / Node.js microservices
  • REST & WebSocket API design
  • LLM agents & tool-calling
  • Data pipelines & search
  • Stripe billing
GoPythonPostgreSQL · PostGISRedisStripeLLM APIs

SVC.04 // SECONDARY

Cloud & DevOps

Infrastructure as code, not as folklore

AWS estates defined entirely as code with CDK — isolated environments, autoscaling services, CI/CD pipelines, monitoring and security alerting. The same discipline as the 52-stack-type estate I run in production at nHabit, sized to your project.

  • AWS architecture & CDK stacks
  • CI/CD pipelines
  • Observability & alerting
  • Cost & security reviews
AWS CDKECS FargateGitHub ActionsDockerTerraform
[ FIG.02 ]THE PROTOCOL

From first call to launch

SEQ.01

Discovery

A call to map what you're building, why, and what success looks like. You get a written scope with honest estimates — not a sales pitch.

SEQ.02

Architecture

System design, stack selection and a delivery plan sized to your budget. Prototypes where the risk justifies them.

SEQ.03

Build

Short iterations, working software from week one, progress you can click on. Tested, documented, CI-gated code — the kind I'd hand to my own team.

SEQ.04

Launch & beyond

Store submissions, deployment, monitoring, analytics. Then either a clean handover to your team or ongoing iteration — your call.

[ FIG.03 ]ENGAGEMENT READOUT

The terms, in plain text

~/alessio/engagement.conf[ LOADED ]

01ENGAGEMENT: PROJECT | RETAINER
02LOCATION: LONDON + REMOTE
03RESPONSE_TIME: <24H
04FULL_TIME: DECLINED
05# scoped builds · monthly retainers · technical advisory

Most work runs one of two ways: a scoped project with a defined deliverable and an honest estimate, or a monthly retainer for ongoing product engineering. Either way you get tested, documented, CI-gated code — and a reply within a day.

SYS.INPUT // AWAITING BRIEF

Tell me what you're building.

A reply within a day, a written scope within 48 hours, working software soon after.