Context:
We rebuild the website, brand and strategy and they're now stable. The key question became: what’s our first real product? The answer: pipelines.

Decisions Made:

• Chose pipelines as Reposible’s first product, built in a visual-first way (“Make.com for pipelines”)
• Continued shaping the repository and platform structure
• Applied the 5 percent rule: polish every detail until it matches our envisioned level
• Set a goal to launch an MVP by September
• Expanded the website with a Playbook to share design, strategy, marketing and development notes
• Made community visibility a priority (Discord, personal introductions, open feedback loops)

Outcome & Learnings:
Pipelines became the tangible foundation for everything that follows. The Playbook opened our process, and community engagement grew.

‍Context:
Conversations shifted from “how to sell” to “what we want to build.” A talk with our former colleague Nick triggered the key pivot: Reposible needed to be bigger, clearer, and true to who we are.

Decisions Made:

• Pivoted from “integrations as a product” to an open-source model with repository management as the foundation
• Expanded product scope to include pipelines, rulesets (to be), and dependencies (to be)
• Committed to open source in everything: not just code, but process, ideas, lessons learned, ...
• Redefined tone of voice to be clearer and more human
• Decided to bring the team’s personality forward on the website and community channels

Outcome & Learnings:
This pivot clarified Reposible’s identity: transparent, open, and human. The direction felt right and gave us renewed energy to keep building.

Context:
The first month of Reposible. Together with Bert, we combined our skills to launch a template of ready-made integrations, aiming to help developers avoid rebuilding the same logic repeatedly.

Decisions Made:

• No paid advertising, focused on early adopters and feedback
• Defined pricing tiers: Foundation (€0), Core (€49), Pro (€149), and Extend (€5/month)
• Started early feedback loops via Reddit and Discord
• Realized integrations alone wouldn’t sustain the product, began exploring a broader scope

Outcome & Learnings:
The launch validated that developers liked the concept but wanted more than integrations. Feedback revealed our story lacked transparency and depth. This was our first real pivot moment. We decided to rethink what Reposible should stand for.