Built for the handoff nobody wanted to manage manually

AppHandoff was built by developers who experienced the AI prototype-to-production gap firsthand. After watching multiple teams struggle to ship Lovable and Bolt prototypes to real backends, we built the coordination layer that was missing: shared context via MCP, agent-published contracts, and a Kanban board where agents and humans work side by side.

The dangerous part of AI-assisted delivery is not code generation. It is the gap between one repo's assumptions and another repo's reality. A Lovable frontend calls endpoints that the backend has not implemented yet. A backend refactor changes a response schema that the frontend still expects in the old shape. Neither side knows about the other's changes until staging blows up.

AppHandoff treats that gap as a first-class workflow with published contracts, tickets, and reviewable plans. Agents publish the API contract as they build, so the other side codes against the real shape instead of a guess. Handoff tickets carry the endpoint path, acceptance criteria, and who has claimed it. Implementation plans are drafted with project context so the fix is unambiguous.

The product leans toward machine-readable context, visible claims and proof that work actually shipped, rather than opaque background automation. Agents draft; humans approve. Every action is auditable.

We favour small, reviewable changes over large batch deployments. Every feature ships through a pull request, every agent action is logged, and every implementation plan is visible to the next person who picks up the ticket.

We are based in the Netherlands and operate as part of Team K2K. The platform is built for solo developers, agencies managing multiple client projects, and engineering teams integrating AI tools into their existing workflows.

AppHandoff is built and operated by Inspired by Frustration, the AI-engineering studio of a fractional AI CTO running a production agent fleet — the same workflow AppHandoff coordinates is the one that ships AppHandoff itself.

The product is built on a conviction that AI coding agents are most valuable when they operate within guardrails. Agents should not commit directly to production branches. They should work from a scoped ticket, open pull requests, and leave the big calls to people. AppHandoff holds its own high-impact moves, such as approving a milestone or moving work between projects, until a human approves them; merge protection stays with your repository host.

When an agent connects to AppHandoff via MCP, it gets structured access to the project state it needs: project rules, published contracts, open tickets, milestones, and implementation history. It does not need to infer project state from file trees or README prose. The context is structured and tool-accessible.