CTO & co-founder, Venture Engine Stockholm | co-founder seat | equal split

Hi, I'm Robin. I run Spucce Venture (spucceventure.com), a venture studio in Stockholm. I'm looking for two co-founders to build the next chapter with me: a tech partner and a business partner. This post is about the tech/CTO seat.

How it's set up

There are two parts.

Spucce Venture is the studio. It builds, runs, and scales companies. It holds the network, the partners, the pilot customers, the investors, the brand. That part is already standing.

The Venture Engine is the first company the studio builds. It's the operating system that every venture we launch will run on. Not a SaaS tool. Not another AI wrapper. A digital twin of the whole process of building a company, from idea to formation to daily operations.

The Venture Engine is where you come in. Three co-founders. Equal split. One seat is yours.

What it is, technically

Persistent memory that compounds over time. Agent orchestration. Modular workspaces. Automation layers. A credit economy. Identity and permissions. Cross-venture intelligence.

The better the engine, the more companies we can run with fewer people and less capital. That's the whole point.

Where we are

I've done a lot of the groundwork so you don't start from zero.

• working prototype and live demo

• backend architecture mostly in place

• product architecture documented

• concept, vision, and brand done

• investor materials and investor portal live

• pre-seed closed, seed in progress

• 10 + pilot customers ready to test

• 100+ verified entrepreneurs ready for alfa

• 600+ verified entrepreneurs ready for beta

  
  

What I need from you

A builder. Someone who can take the car apart on the garage floor, understand every part and put it back together so it runs better. Not someone who just can drive it.

• you open the current codebase and know within days what stays, what goes, and why

• you set the architecture and the stack, then write the first version yourself

• you take a product idea from a whiteboard sketch to a build plan to running code, in the same week

• you build AI first. Agents, memory, and orchestration are the core of the system, not a layer on top

• memory returns the wrong context, you trace it through the pipeline and fix the design, not the symptom

• an agent loop is slow and expensive, you rewrite it so it costs less and runs faster

• ten ventures need workspaces on one engine, you design the permission model so it holds at a hundred

• you close loops. Data flows in, the system learns, the next decision is better. You design for that from day one

• you know when to build, when to buy, and when to wait, and you can explain the cost of each

• you see where the tech is going before it's obvious. Models get cheaper, agents get autonomous, code writes itself. You build for that world, not the current one

  
  

Prompting is not engineering. You read code. You write code. You understand systems from the database up to the interface.

Just as important: you have your shit together. You can hold yourself when things get rough. You don't need someone to manage your mood or your motivation. You work on yourself the same way you work on the code. You keep your word. You show up.

You

• full-stack engineer with strong system design instincts

• shipped production AI or ML systems

• RAG, vector databases, memory architecture

• multi-agent coordination, event-driven systems

• cloud infrastructure, security, identity at scale

• has led engineers and shipped 0 to 1

• calm when things are unclear, quick when things need to change

• based in Stockholm. This one is not negotiable'

  
  

What you own

The entire technical layer. Architecture, stack, priorities, AI infrastructure, security, performance. You take the engine from alpha to full system.

The deal

• equity: equal split of the Venture Engine between three co-founders

• salary: none until we close the investment round. This is a startup. We work until the money is in. Then salaries follow.

• location: Stockholm, in person. The early phase needs it.

• role: CTO and co-founder. Board involvement. Real say in product, capital, and direction.

• after that: the Venture Engine is company one. The studio builds more. If we continue to keep on working what we created in the venture engine, we move your equity/shares to the studio to scale more ventures .

The engine is the start. Once it runs, we use it to build the next company. Then the next. Every venture adds memory to the engine. Every launch makes the next one faster and cheaper. In a few years the studio runs a portfolio of companies on infrastructure we built ourselves, with a small team, and most of the world still thinks that's impossible.

That's the adventure. Not a product launch. A new way of building companies, tested on ourselves first and our first pilot/alfa/beta testers.

It won't be smooth. There will be months with no money, weeks where everything breaks, days where we wonder why we started. That's the deal. I'd rather do it with someone who wants that than someone who wants comfort.

If this sounds like your kind of trip, write to me.

Robin