Technical Delivery Lead — ship discipline for a small, AI-first software team

We're a profitable, founder-led B2B SaaS company. Our product helps professional buyers aggregate data on items in marketplaces. Five developers, several products shipping in parallel, real runway, and a defined window to get a specific set of things built and shipped. Here's the honest part, and the reason this role exists. Our speed has outrun our process. We're good at building. What hasn't caught up is the discipline around the building: sequencing parallel work, gating what ships, and documenting it so it repeats instead of getting re-improvised every feature. Today most of that routes through the founder and the lead developer personally, which makes them the bottleneck and lets work slip. You won't be untangling years of bureaucracy. You'll stand up the delivery function for the first time, for a team that earned the problem by moving fast. What you'll own 1. The build pipeline end to end: mockup to spec to GitHub (with CI and AI-assisted workflows) to shipped. Make it repeatable. 2. Sequencing the parallel threads and holding scope against real dates. 3. Release and QA gating, and verifying that "done" is actually done against the running system before anyone calls it done. 4. Turning dev-meeting decisions into tracked tasks with clear owners and dates. 5. Over time, consolidating today's scattered dev syncs into one clean rhythm. What you won't own Our stack GitHub with CI, ClickUp for tracking, a Windows desktop application and a web application shipping in parallel, and AI-assisted development workflows throughout. Scrappy is fine. We're not looking for anyone to rip and replace what's working. You're the right fit if you 1. Have shipped real software and can hold your own in an architecture or trade-off conversation, enough that engineers respect you. 2. Measure yourself by outcomes driven and blockers removed, not by meetings run. 3. Are comfortable with little process and an AI-first team. 4. Earn trust with one visible win before proposing broader change. 5. Communicate clearly in English. How we expect to start A paid 30-day scoping engagement, part-time, roughly 1 to 2 days a week (align with ET working hours). You learn the system, find where work slips, and ship one visible win: getting our disabled CI test gate back on, making it impossible for a dev build to reach production by accident, and standing up basic outage alerting. You deliver a short charter and a sequencing and release-gating recommendation. From there we decide together whether to expand the engagement. This is a seat, not a task. It's built to grow.