AI Workflow Builder

/ FOR THE BUILDER WHO WANTS TO TURN STUDIO WORKFLOWS INTO AI-ASSISTED SYSTEMS THAT SCALE

You

• You are a hands-on builder. You have shipped real working things — not diagrams, not plans, not slides. You can build a prototype on Tuesday and have someone using it on Wednesday. The years on your CV matter less than the reps. Someone who has been deep in this for one intense year is as interesting to us as someone who has done it for five.
• You are AI-native in how you work. LLM APIs, prompt chains, structured outputs, human review loops — these are tools you have used enough to have opinions about. You know where they shine and where they break. You can break a messy advisory workflow into discrete input, processing, review and output steps, and you can build each step cleanly.
• You have product restraint. You can tell the difference between a workflow that needs to be reliable for ten people inside the studio and a feature that needs to be productised for the world. You build for the former first. You do not introduce heavy tooling unless it materially reduces the work the studio is doing today. You know when to stop.
• You can convert vague strategic material into clean operating formats — a half-coherent founder transcript into a structured brief, a long debrief into a sharp sprint story, a folder of partner emails into a relationship map. Strong written structure is part of how you build, not a separate skill.
• You are mature about confidentiality. You understand that the studio's work touches founders in vulnerable moments, capital partners with reputational stakes, and impact data that can be misread. You build with access boundaries in mind from the start.
• You care about impact. In the way someone cares when the workflow they shipped means a sprint lead got home for dinner and the founder still got the support they needed.

The studio

World Impact Practice (WIP) is a venture studio solving the world's hardest problems with the right founders, sprint by sprint.

The team behind WIP co-builds every sprint with the founders and companies. Our core team of ex-founders, operators and investors has spent the last three decades building some of Europe's most profitable fintech and trading companies, and the last several years applying that same rigour to global impact - alongside organisations like the Rockefeller Foundation, UNDP, Brown University and Secrid. Eighteen years of boots on the ground. Forty-two ideas built to impact. Eighty-nine thousand build hours invested. Two million lives touched directly.

Every sprint we run produces work that repeats. Founder intake conversations. Transcript synthesis. Document extraction. Stakeholder mapping. Sprint output preparation. The strategic judgment in each of these is human. The mechanical work around the judgment is not — and that is where the studio is bleeding hours we should be investing somewhere else.

Why this role exists

WIP is building the technical backbone that lets a team of eleven do the work of a hundred. The CTO owns the architecture — ingestion pipelines, retrieval layers, the impact calculator, the studio knowledge base. This role sits one step closer to the day-to-day work of the studio. You will be the person who looks at how a sprint actually runs, finds the repeatable patterns, and turns each one into a workflow that does the mechanical work without dulling the strategic judgment that runs underneath it.

The role has three rhythms.

• First, you build efficiency. Lightweight AI workflows that handle the mechanical work — transcript processing, document parsing, prompt chains for structured output, comparison layers, draft preparation — with human review built in at the right points. You version what you build. You make the outputs editable and traceable. You separate internal-facing tools from anything that touches a client without review. You ship workflows that the studio actually uses the next morning, not prototypes that get demoed and forgotten.
• Second, you experiment with Intelligence. We believe AI has still not be used with its deepest potential of intelligence in the world of humans x plant x impact. We are constantly dabbling with new hypothesis of models/ logics and frameworks to bridge the gap of impact through AI. You are expected to work alongside psychologists on one day and statisticians on another.

The work compounds in a specific way. Each workflow you build buys back the studio spends on elevating its strategic work — sharper sprint design, deeper founder support, more defensible impact claims. The compounding is the point. The studio's ability to take on the next sprint, and the one after that, depends on it.

What you'll work on

• Workflow mapping.  Sitting alongside sprint leads and watching the work happen. Identifying what repeats. Distinguishing the steps that benefit from AI assistance from the ones where AI creates new risk.
• Transcript and document workflows.  AI-assisted processing of founder calls, sprint debriefs, partner conversations and client documents — into structured, queryable, reviewable outputs.
• Extraction and structuring.  Turning raw founder inputs — decks, research, scattered notes — into the studio formats that sprint leads can actually pick up and run with.
• Comparison and review layers.  Workflows that surface differences across versions, across sprints, across founder cohorts — so the studio can see patterns it would otherwise miss.
• Output preparation.  Lightweight workflows that take rough strategic material and turn it into clean operating formats for review, without producing anything client-facing without a human in the loop.
• Prompt and workflow versioning.  Every workflow you build is editable, traceable, and improvable. You set up the practices that keep the system trustworthy as it grows.
• Confidentiality and access boundaries.  Founder material is sensitive. Client material is sensitive. You build with that in mind from the first commit.
• Cross-pollination with the CTO and the Innovation Partner.  Your workflows feed into the larger architecture. You shape what the backbone needs to do, and you build on top of what it gives you.

Stack is deliberately lean: Anthropic API, prompt chains, structured output, lightweight tools where they earn their place — Notion, Airtable, Make, n8n or similar — and code where the lightweight tools fall short.

What this role offers

• A real piece of infrastructure to own. The CTO owns the architecture; you own the workflows that make the architecture useful day to day. Your work is what the studio touches every morning.
• Direct exposure to the founder of WIP, the CTO, the Innovation Partner, and the sprint leads who are running the studio's most experimental work. The internal tools you build become studio IP. The workflows you ship become the operating system of how the studio runs.

**

How to apply**

Send us what you have built. A workflow, a prompt chain, an internal tool, a scrappy automation that shouldn't work but does. And short note on why WIP and why now.