“Did you send the invoice?”
An importantproduct idea.One team to solve it.
x Create helps founders, owners, and operators decide what should exist, design and build it, then hand it over or keep it running under clear terms. The result could be a website, store, app, platform, portal, internal system, integration, or automation.
Start with
The problem or idea
Decide
What should exist
Build
The first useful version
After launch
Handover or managed operation
Local time
--:--:-- SAST
Status
Online
Right now: duct tape.
Less chasing. More control.
Which bookings are actually confirmed?
Call Marius back — Tuesday?
47 unread. Which three matter?
The cottage is booked twice.
Where is that proof of payment?
Shubble
transport
School transport, all connected.
Shubble brings families, drivers and the operations team into one connected transport platform. Parents can arrange and follow trips, drivers know exactly what their day looks like, and staff can manage the whole service without chasing updates across different tools.
See what changedMoteef (x Create product)
saas
Your brand, remembered.
Moteef gives a business one place to plan, create, review and publish its marketing. It learns the brand once, carries that context into every task and keeps the team moving without rebuilding the same brief in five different tools.
See what changedCustom Point of Sale
retail
The counter and back office, connected.
This point-of-sale system was built around the reality of a busy shop floor: weighted and unit products, quick payments, morning stock counts, WhatsApp receipts and an owner who still needs to understand exactly what happened at the end of the day.
See what changed
Useful from day one. Designed for what comes next.
No mystery. Just a clear way forward.
You should always know what we're building, why it matters, and what happens next.
01
START HERE
Bring the real problem or idea.
You do not need a polished specification. Explain what should be possible, what is getting in the way, and why solving it matters now.
02
DECIDE
Work out what should exist.
For clear, bounded work, we scope the build directly. Where the risk or uncertainty is material, a Solution Blueprint defines the users, rules, first release, ownership, and operating model before the build begins.
03
BUILD & LAUNCH
Get the first useful version working.
We design, build, test, and launch in visible stages. Scope, decisions, dependencies, and running costs stay explicit so speed does not create a hidden support tail.
04
CHOOSE THE RELATIONSHIP
Make responsibility explicit.
After launch, choose a clean handover, defined managed operation, or a Product Partnership for substantial ongoing product responsibility. New work is scoped and paid unless the agreement includes it.
Small team. Direct answers.
FIG. 06 — THE PEOPLERijn leads the product, UX, commercial, and technical decisions on substantial work. The wider team extends business development and distribution without placing account-management layers between the client and the people responsible for the outcome.
Rijn Hartman
Founder & Solutions Architect
Connects the business problem, product decision, user experience, commercial model, and technical approach from first conversation through operation.
Nick Kornieck
Business Development
Opens and develops relevant conversations with businesses in the United States.
Chris Kaniki
Marketing & Growth
Develops the content and distribution systems that turn useful work into relevant conversations.
Have an important problem or product idea? Start a conversation.
01
Decide
Work out what should exist, what should not, and the sensible first release.
02
Design
Shape the user experience and business rules before they become expensive code.
03
Build
Create the website, store, app, platform, portal, integration, or system.
04
Operate
Hand it over cleanly or keep it running under a defined monthly agreement.
START WITH THE REAL PROBLEM OR IDEA
What should
exist next?
You do not need to arrive with a finished specification. Explain the problem, the opportunity, and why it matters. We will help identify the smallest responsible route forward.
DECIDE WHAT SHOULD EXIST. BUILD IT WELL. KEEP IT USEFUL.



