Loading
Loading page content…
Mr Iridescent 2026Creative Renaissance Man
Loading
Fractional CTO · strategic systems partner
Most founders do not need a full-time CTO. They need a systems strategist who can find the hidden leverage, de-risk the build, and deploy targeted micro-solutions. I take technical ownership on a monthly retainer and leave your team stronger than I found it.
The shape of it
30-60-90 days
Weeks 1–2: audit the architecture, spend, and risk.
Month 1: decide what to build, buy, or switch off.
Months 2–3: ship the smallest useful systems and hand them over.
Based in Lagos, Nigeria; working with teams remotely. Scope and fees are set after discovery — no invented packages.
The problem
Most operational friction is not a coding problem. It is a set of small, unowned gaps between systems, teams, and decisions. The first job is to make them visible.
Payments, inventory, and bank records disagree by small amounts that compound. Nobody owns the reconciliation, so the loss stays invisible until month-end.
Skilled people spend the week copying between spreadsheets, inboxes, and CRMs. The process lives in someone’s head, and it leaves when they do.
Every team buys another SaaS. Nothing talks to anything else, and the subscription bill grows faster than the capability it was meant to buy.
Hourly agencies are rewarded for overbuilding. You are left with a codebase nobody can explain and a maintenance bill that never ends.
What I own
The 30-60-90 day blueprint
Every engagement starts with evidence and ends with something your team can operate. No 80-slide deck that never becomes a system.
Phase 1 · weeks 1–2
01
I look behind the technology veil: cloud infrastructure, SaaS spend, code quality, data flows, security posture, and the manual workarounds holding the operation together.
Output: Architecture map, risk register, and a prioritised list of where money or uptime is leaking.
Phase 2 · month 1
02
We decide what must be built, what should be bought, and what should be switched off. The goal is to protect runway and stop paying for complexity you do not need.
Output: Target architecture, procurement recommendation, and a 90-day delivery roadmap.
Phase 3 · months 2–3
03
I ship the smallest systems that remove the bottleneck, then document them and train the team that will own them. Your developers get stronger; the dependency on me gets smaller.
Output: A working microservice, runbook, handover session, and an upskilled team.
Retainer tiers
Three levels of involvement. Each includes the one below it, so the engagement can grow without renegotiating the relationship.
Tier 01
Architectural oversight & vendor management
Early-stage startups and non-technical founders
Tier 02
Engineering leadership & strategy
Growth-stage businesses, roughly 10–25 people
Tier 03
Deep-tech architecture & autonomous systems
Scale-ups, logistics, e-commerce, and public infrastructure
Fees are set after a short discovery conversation. I do not publish invented packages or promise outcomes that depend on access I have not seen.
Who it fits
The technical work is similar; the buying trigger is not. The first conversation starts with the pressure you actually feel.
The pressure: Infrastructure decay, delayed reporting, and audit compliance.
The offer: Civic diagnostics, edge AI sentinels, and low-friction public-works oversight — where procurement and access allow.
The pressure: Legacy modernisation, fragmented tools, and security risk.
The offer: Architecture audits, high-throughput services, and zero-trust workflow bridges.
The pressure: Cash-flow leaks, manual inventory errors, and agency costs.
The offer: Turnkey reconciliation, WhatsApp event bridges, and micro-SaaS integrations.
The pressure: Burn-rate pressure, non-technical leadership gaps, and overpriced agencies.
The offer: Fractional CTO governance, rapid MVP de-risking, and a 30-day technical roadmap.
Microservices
Not everything needs a platform. Often the highest-leverage move is a narrow service that closes one expensive gap and stays cheap to run.
A scheduled worker that pulls payment, inventory, and bank data, flags mismatched micro-transactions, and alerts operations before month-end.
Permission-aware monitors for pricing, tenders, listings, or supply-chain signals, normalised into a dashboard or sheet. Built only where access and terms allow.
An event gateway between the CRM and messaging channels so order updates, ops alerts, and high-value leads reach a human immediately.
An internal tool where staff drop PDFs, voice notes, or spreadsheets and receive structured summaries, action items, and risk notes.
Every build is scoped for lawful access, data minimisation, and a clean handover. I do not scrape private data or leave a system that only I can operate.
Next step