Palahepitiya Gamage Amila · Method
How I work as an AI-first fractional CTO
I work as an AI-first fractional CTO. You hire someone who owns the technology seat, not someone who leaves slides and walks away.
Agents and specialists collect the facts and write drafts. I decide. We run the work together. Anything that goes outside the company waits for your approval.
What the seat means
Most founders do not need another advisor. They need someone who will make the call (ship this, stop that, hire here, wait on that) and still be there next week when those choices matter.
That is the fractional or interim CTO job. Below is how I do it without pretending one person can read every line alone.
Collect and draft
Tools and specialist workflows pull from the places that usually bury leadership.
- Code and pull history
- Architecture and infrastructure docs
- Product, roadmaps, and support patterns
- How fast the team can actually deliver
They collect. They draft. They surface risks and options. They do not decide. The point is simple: cover more ground, faster, so senior time goes where it changes the outcome.
Decide
I read what comes back. I throw out noise. I check what needs a human eye. I decide what matters for your stage, not for a textbook company.
Then I lock the decision. That is what you hire. A fractional CTO who will not decide is just an expensive sounding board.
Keep the company moving
Between meetings, work still has to move.
- Priorities that hold up for the week
- Clear owners on the work that matters
- A way to reach me before a small problem becomes a big one
- Continuity so people are not waiting for the next call to act
I lead with you, and with the people who will still be there when the retainer ends or turns into a hire.
Your approval before anything external
Inside the company we move quickly. Outside, nothing goes out under your name until you approve it.
Drafts can be prepared. Nothing material goes out without your say-so. That includes messages, recommendations that bind the company, and anything that could end up in a board pack or a customer conversation.
Build safely
Cloud coding agents and AI tools help a small team ship more. They also create new ways to leak secrets, skip review, or rewrite the wrong thing.
So we draw clear lines:
- Where agents may draft and propose
- Where passwords and production access stay controlled
- Where a human must review before merge or release
Fast where the lines are clear. Careful with secrets, production access, and anything that merges or ships.
Two audiences, same person
With the team
Concrete decisions, architecture trade-offs, delivery pressure, and growing people into leads.
With founders and the board
Plain language on risk, cost, capability, and speed, so technology is not a black box when money or strategy is on the table.
Same person. Same facts. No soft rewrite in between.
How this connects to setup
If the retainer is the seat, AI-first engineering leadership setup puts the habits around it: draft workflows, decision rhythm, approval rules, and safe coding and secrets limits, in a bounded multi-week setup.
Some founders start with setup, then move into retainer. Some start in the seat and tighten the system as we go. A short discovery call sorts which path fits.
If you are in Manchester or Greater Manchester, see Fractional CTO Manchester. When capital is moving, the same judgement is technology and product due diligence.