Sam
Founder · CEO
Decades of operational and compliance experience across South African SMMEs. Sam keeps the technical work pointed at outcomes that matter rather than shiny distractions, and leads our Client Success team.
Built deliberately.
A small team of architects and specialists. South African by base, international in reach. These are the principles, the values, and the people behind the work.
Sixees Labs is a team of solution architects working in the AI era — boutique by choice, multidisciplinary by composition, deliberately small. We sell experience, not hours. This page covers who we are, what we believe, how we work, and the people behind it. If anything on the services page sounds like something you need, this is the page that tells you whether we're the right team to do it.
01
a-01
Who we are
A boutique practice, intentionally small.
We are architects and specialists — past the stage where titles need to do the work. Our combined experience runs into decades of designing, building, and operating production systems for enterprise and product companies. What we sell now is that experience — applied to the question of how AI moves from a strategy slide into shipped product. We are small because we choose to be. Staying small means we say no to work that doesn't fit, and the work that does fit gets the attention it deserves — from the people you spoke to at the start, not a delivery team you've never met.
What we are
- +Architects and specialists, end-to-end
- +Boutique by design
- +Hands-on practitioners, not advisors-only
What we choose
- +Long-term client relationships
- +Honest scoping over inflated proposals
- +Outcomes over hours
What we avoid
- —A sales team between you and the people doing the work
- —Pure strategy decks with no implementation
- —Junior cohorts learning on your project
In numbers
Decades of combined production systems work · senior team throughout · single-digit client roster at any time
02
a-02
What we believe
Five values. Each one is a phrase, not an abstract noun.
Values matter not because they're written down, but because they decide what we do when the right call isn't obvious. These five came out of how the team actually operates on its best days — and they're how we hold ourselves to it on the harder ones. We refer to them by hashtag, on internal walls, in retrospectives, and in the conversations we have when something has gone wrong.
#OneTeam
Trust is our currency.
We win together, and when we lose, we lose together. We hire people we believe are capable and acting in good faith, and we extend that trust by default. The team carries each other when energy runs low. Internally we name who made the difference. Externally we present a team that got better.
#ShipWithPurpose
Impact over output.
We ship things that matter. When a new requirement appears, we ask why before we ask how. We question scope creep — kindly, but we say it. We hold a high bar for craft, but "done well" is not the same as "perfect". A small thing in production beats a grand thing in someone's head.
#OwnIt
Full accountability, without being asked.
If you see it, you own it — at minimum to surface, often to fix. "That's not my job" isn't a phrase we use. When something goes wrong, the question is not whose fault it was. The question is what we do now, and how we stop it happening again. Names appear in the credit list, not the blame list.
#StayCurious
The best practitioners are permanent students.
The technology underneath what we build is moving faster than any of us has experienced. Curiosity is a discipline we practise, not a personality trait we hire for. We're confident in our areas of strength, and humble enough to listen when someone offers a perspective we hadn't considered. Knowledge that stays in one head doesn't compound.
#StraightTalk
Direct, honest, kind.
We default to telling each other the truth — about the work, the deadlines, what's going well, and what's not. Direct and kind aren't opposites. The real cruelty is letting someone discover a problem they could have fixed weeks earlier. With clients, with each other, with ourselves — we don't dress things up.
Where these came from
Not handed down by management · drawn from how the team actually operates · refined into something we can hold ourselves to
03
a-03
How we work
Boring infrastructure. Sharp judgement. No theatre.
How we run a project matters more than how we describe it on a website. The commercial model — fixed-fee, outcome-scoped, no account managers — sits on the services page. This is the operating model underneath it. Three things that are non-negotiable in how we run the work.
Before
- +We scope honestly, including what we wouldn't build
- +We tell you when AI isn't the answer
- +We agree what "done" looks like before we start
During
- +Weekly check-ins with a written status
- +Bad news travels first — never at the deadline
- +We work in your language, not ours
After
- +You own the code, the models, the data
- +We document what we built and how to run it
- +We're available afterwards, no retainer required
What that means in practice
Status updates with the bad news included · no surprises at delivery · clean handovers you can run without us
04
a-04
Where we're from
South African by base. International in reach.
We're headquartered in the Western Cape, with the team distributed across South Africa. We serve clients here at home and across multiple continents — Europe and North America most often. Local presence means we can sit in the room when it matters; the distributed team means we can hand off across time zones when a client needs it. POPIA-compliant by default. GDPR-aware in practice. Cross-border data flows and residency requirements are something we've already thought about.
Local
- +Western Cape headquartered
- +In person when it matters
- +POPIA compliant by default
Regional
- +Clients across South Africa
- +Time zones that work for European hours
- +English-first, multilingual where needed
International
- +Clients in Europe and North America
- +GDPR aware
- +Distributed team for extended hours when required
Practical detail
Registered in South Africa · billing in ZAR, USD, EUR, GBP · data residency options for regulated industries
05
a-05
The team
Senior. Hands-on. Named.
We don't have a wall of headshots, and we don't pretend the company is bigger than it is. The team that scopes your project is the team that does the work. The people you talk to in the first call are the people you talk to in the last one. Below are the senior people directly involved in client engagements. When the team grows, it grows here.
JP
Founder · Principal Architect
Decades of designing, building, and operating production systems for enterprise and product companies, now focused on helping teams turn AI from strategy into shipped solutions. Sits on every engagement from scoping through hand-over.
Zenia
AI Systems Architect
Nearly a decade building UX-focused applications for SaaS companies, now delivering the automated workflows and AI solutions that actually matter. Zenia leads our agentic development work, from scoping through hand-over to the feedback and refinement that follows.
Hiring posture
We hire slowly · for #OneTeam over individual brilliance · senior-only at present · we'll say so on this page when that changes
Want to find out if we're a fit?
A short call about what you're working on and whether we're the right team to help. No proposal unless you ask for one.
- Format 60-min video call
- Output Honest read
- Commitment None required
- Availability Q3 · open