Architecture
The data model, the service boundaries and the build-versus-buy line on authentication, payments, search and the other components a team is tempted to write itself, decided before they become expensive to change.
The engagement covers the architecture, the first engineering hires, a technical due diligence or the design of your AI infrastructure, from a few hours of consultancy to an interim CTO at half-time. Each format runs on a services contract, invoiced monthly, with 30 days' notice.
Two days a month covers the decisions. A day a week adds follow-through with the team.
A fractional CTO takes the decisions that belong to the CTO role, part-time: the architecture, the first engineering hires, technical due diligence with investors and the AI that goes into the product. The time commitment runs from consultancy by the hour to half-time, and in every format the CTO signs the decisions and answers for them.
An interim CTO covers the role at half-time or more for a fixed period, while you recruit the permanent CTO, and hands over when they arrive.
The engagement runs on a services contract with monthly invoicing and 30 days' notice, so there is no recruitment process and no probation period. Four steps take you from the first message to the first working session.
Describe the decision in front of you: an architecture that has to hold for two years, a hire nobody on the team can assess, a funding round, an AI feature. A CTO reads it and replies within 24 hours.
With the founders or whoever owns the decision. It ends with a recommended format (advisory, fractional or interim), or with the conclusion that you do not need a CTO yet.
An hourly rate invoiced monthly against a retainer. No recruitment fee, no equity, no exclusivity; the monthly figure is in the proposal before you sign.
In English or Spanish, on European hours. The first written deliverable (an architecture review, a hiring bar or an AI roadmap) arrives within the first month, and the time commitment moves up or down as the company changes.

The data model, the service boundaries and the build-versus-buy line on authentication, payments, search and the other components a team is tempted to write itself, decided before they become expensive to change.
Who interviews them, where the hiring bar sits and which senior engineer sets the standard the rest of the team codes to. Conectia's own bar admits 3% of applicants, after CTOs assess their architecture, production code and references.
Sales needs the integration, marketing the dashboard, the CEO the mobile app. Someone with the decision rights says what is feasible this quarter, in what order, and which request should never be built.
Which model, at which layer, under what fallback, with evals and a cost ceiling, and which parts of the workflow stay human. A demo costs nothing to get wrong; a feature billing tokens on production traffic does.
Due diligence in both directions: the one investors run on you before a term sheet, and the one you run on a vendor or on the codebase an agency left behind. It includes the technical account of the company you present to investors.
When the decision is made and it is time to execute it: custom software development → · forward deployed engineers to take AI to production →

CTOs and principal engineers who have held the technical role at executive level.
Each engagement is matched to the decisions in front of you: the architecture, the hiring loop, the investor meetings, a migration that has no owner yet. Conectia's own CTO leads some engagements and CTOs from our network lead the rest; either way, the CTO who leads it is the one who signs the decisions.
When a decision needs a second senior view, another CTO from the network joins the engagement.
MintID: a squad of three engineers plus a CTO, embedded since March 2026, building the protocol core and the verifier SDKs.
Ealyx, Barcelona: circularity software for e-commerce. A Conectia team has carried the product from idea to production and keeps building it, as one team with the founders.
Bonus Iuri: contract risk analysis backed by Spanish legislation. The founder brought the domain; the CTO brought the architecture, the model choices and the team.
Architecture reviews, the hiring interviews, and board and investor preparation.
When it fits: the decisions come a few at a time and the team can carry them out between reviews.
Runs the operating cadence: a weekly sync with the founders, the engineering rituals and the pull requests that matter, and unblocks the mid-level engineers.
When it fits: the team has crossed five engineers, or AI is in front of users, and someone has to review the quality bar, the evals and the cost limits every week.
Leads the team, speaks for engineering to the vendors and the investors, and stays in the code: the architecture the interim CTO defends is one they wrote.
When it fits: a funding round, a diligence window or a CTO vacancy needs the role covered for six weeks, sometimes a quarter.
Every format is billed by the hour and invoiced monthly against a retainer.

TALK TO A CTO
The architecture, the hire, the round or the AI feature in front of you. The reply recommends a format, or tells you that you do not need a CTO yet.
The rate and the monthly figure come in the one-page proposal, after the one-hour call.