UK · Simon Piscitelli, technology director

Fractional CTO and CPO. Someone senior owns the calls.

Your first version has been nearly done for months. Every change costs more than the one before it. Your biggest project is a year late and the plan on the table is more engineers. You need someone senior to judge the technical calls and own what happens next.

Book the exploratory call
Who it is for

The seat your business needs.

The seat

You need someone to own the technical calls.

You are taking a product from an idea or an MVP to an established business. Or you own a software-led company of 10 to 50 people or larger, where the technical calls are being made without anyone senior to judge them.

Any stage, pre-seed to Series C. Simon holds the fractional CTO or CPO seat, or takes an interim engineering director role for a programme that needs him.

For a board or an investor who needs a read without an operating role, see the technical adviser page.

What the consultant provides

Five jobs. One seat.

Technical advisory, hiring, strategic vision on technology and product, the technical roadmap, and running your software build team. Simon holds the seat and makes the calls.

Technical advisory
The rebuild, the supplier's estimate, the architecture, the technical question before a fundraise. A senior read on what the decision means for cost, speed and risk.
Hiring
The first engineer or the senior hire you have never made. Simon judges what the function needs and who can do the work.
Strategic vision on technology and product
What to build and why, drawn from customer signal and the business you are growing. Technology and product direction sit in the same seat.
The technical roadmap
The priorities and the sequence, from the founder's sales calls to what the team ships. Someone senior owns what comes next.
Management of software build teams
Your own engineers or a supplier's, under Simon's oversight. He runs the build team and reads and writes code where the judgement needs it.
How it starts

Three steps. The first one is free.

Every engagement starts the same way, whatever mode it ends up needing. You always know what the next step is, how long it takes, and what you walk away with.

  1. 01

    The exploratory call

    Free. Thirty minutes.

    No slides, no pitch. One question: is the Technical/Strategic Review the right next step for the decision in front of you. When it is not, you hear that on the call.

  2. 02

    The Technical/Strategic Review

    Two weeks. Fixed fee, agreed on the call.

    One senior technology director inside your codebase, team and roadmap, then a written verdict you own outright. It is useful if you never speak to PIMASI again.

    • The verdict: the one decision you brought, answered plainly.
    • The state of the engineering function, in business terms.
    • The risk register: what is most likely to hurt the business, ranked by cost.
    • The 90-day plan, sized, whoever executes it.
    • The mode call: which kind of senior leadership the situation needs, and for how long.
  3. 03

    The engagement

    In the mode the Review named. The Review's fee is credited against it.

    A proposal that opens on the Review's findings, not a cold document: advise the board, hold the CTO or CPO seat, stand up the department, or write the code. When the Review says you do not need PIMASI yet, that is the answer you get.

Book the exploratory call
Proof

Proof, no client named.

A late programme

A 27-engineer project about a year behind schedule. Simon took charge as interim engineering director. Inside four months it shipped on the date the business had set.

A product the founder could demo again

A founder who went from avoiding his codebase to demoing it to customers, in under two months. Simon fixed the engine with the founder's team.

A roadmap from customer signal

A roadmap Simon owned from the founder's sales calls to the shipped MVP, sellable inside six months.

Not a fit

A developer by the day. Equity-only advisory.

Simon holds the seat and owns the technical calls. If you need a developer by the day or equity-only advisory, PIMASI is the wrong call, and the free call says so.

Questions we get asked

Frequently asked

What does a fractional CTO take off my desk?

The technical calls you are making without anyone senior to judge them: the hire, the rebuild, the roadmap and the management of your software build team. Simon holds the CTO or CPO seat part-time, with technical and product direction in the same hands.

Can we start when I have an idea and no product yet?

Yes. The seat is for founders taking a product from an idea or an MVP to an established business, at any stage from pre-seed to Series C. The exploratory call establishes whether the Technical/Strategic Review is the right next step for the decision in front of you.

We already have a CTO or a software supplier. Where does Simon fit?

Simon works with your own engineers or a supplier's team. In a larger company with a CTO, he takes an interim engineering director or specialist role for a programme that needs its own senior owner. The Review names the role and the work it needs to own.

What happens if the Review says we do not need PIMASI?

Then you hear it in writing, and you keep the verdict and the 90-day plan whether or not you engage PIMASI. When an engagement follows, it starts from the Review's findings and the Review's fee is credited against it.

Bring the decision in front of you.

A free thirty-minute call. One question: is the two-week Technical/Strategic Review the right next step? When it is not, Simon says so.

Book the exploratory call