x Create (internal)
The behind-the-scenes system we use to run x Create every day
We built one place to manage our own clients, proposals, agreements, invoices, payments and reports. It gives the team and the client a clear view from the first conversation to the final payment, without stitching the story together from separate tools.
Project overview
We built one place to manage our own clients, proposals, agreements, invoices, payments and reports. It gives the team and the client a clear view from the first conversation to the final payment, without stitching the story together from separate tools.
- Client
- x Create (internal)
- Industry
- internal
- Year
- 2026
- Services
- web apps · portals · payments
01 The problem
Client work moves faster when the admin has one clear home.
Agencies often recommend better systems to their clients while running their own work through a loose collection of documents, spreadsheets, invoices and inboxes. We did not want to sell an idea we were unwilling to use ourselves.
There was also a practical cost. A proposal could live in one tool, the agreement in another and the invoice in a third. Payments had to be checked manually. Reports were rebuilt each month. Clients had no single place to see what needed their attention.
None of those tasks is difficult on its own. Together, they create drag across every project. We needed one working system that could carry a client relationship from the first enquiry to the final report.
02 The result
- One client journey
- First enquiry to final payment
- Proven in daily work
- The system runs our agency
Every client has one visible journey
- 01Agreements, invoices and actions stay together
- 02Clients can see what needs attention
- 03Routine reminders and reports no longer need rebuilding
x Create now runs its own client work through the system it recommends to others. Every active relationship has a visible path through intake, agreements, invoices, payments, projects and reporting.
The team spends less time reconstructing admin. Clients have a clearer view of what has happened and what they need to do. Routine reminders and reports happen consistently instead of depending on somebody remembering at the right moment.
For a prospective client, that is the most useful proof we can offer. When we talk about a portal, an internal dashboard or a custom workflow, we can show the version that carries our own business every day.
03 Our approach
What we built
We built one connected system for the full client journey.
Structured intake forms help people explain what they need before a project starts. The relationship and sales area keeps contacts, opportunities, proposals and follow-ups visible to the team.
Clients can review and sign agreements, open invoices, choose card or EFT, see payments and follow their active projects through a private portal. They always have one place to check what is pending and what happens next.
The admin side brings clients, projects, payments, intake submissions and team activity together. Automatic reminders, receipts and performance reports handle the repeatable work without making the client experience feel robotic.
- 01
Structured project and client intake
- 02
Client relationships and sales pipeline
- 03
Proposals and signable agreements
- 04
Invoices, card payments and EFT
- 05
Client and admin portals
- 06
Automatic performance reports
04 System logic
04
How it works
An enquiry enters through the right intake rather than an unstructured email. Once the work is defined, the proposal becomes an agreement, the agreement can be signed in the client portal and the invoice follows in the same journey.
Card payments run through Paystack and EFT remains available because that is how many South African businesses prefer to pay. The system records the payment history and keeps the invoice, receipt and client record aligned.
During the project, clients see their work and action items in the portal. After launch, recurring reports can be generated and sent without somebody rebuilding the same document by hand each month.
The platform has also moved safely from one backend to another while live client agreements and payments depended on it. That migration proved the system is treated as production infrastructure, not a side project.
Operating principle
“We trust custom software with our own business before we ask a client to trust it with theirs.”
Next case — Shubble
A safer, simpler way for families to book and manage school transport