01
"I have nobody to run my technology area"
Every vendor proposes their own thing and you decide blind. The area exists, the invoice exists, the direction doesn't.
Outsourced technical direction
Someone with technical judgment to ask before you sign
Your company's technology decisions are being made in meetings where nobody on your side can evaluate them. We take that seat: we decide with you what to build and what not to, we review what already exists, and we bring order to vendors and priorities.
Decisions with someone accountable, not just an opinion
A review of the software you were already handed
One counterpart facing your vendors
The breaking point
You're deciding on technology with nobody on your side who understands it
It isn't a shortage of vendors: it's a shortage of judgment of your own. Whoever quotes you is the same party that profits from what they quote, and the only way to know whether they're right is to understand what they're saying.
02
"I want to know whether my software is well built"
It works, but every change takes longer and costs more. Nobody from outside has ever looked at it with technical eyes.
03
"They’re going to charge me a fortune and I don’t know if it’s worth it"
You have a big proposal on the table and no point of comparison. Signing or not signing is a bet.
How we work
Where you notice having technical direction
We don't show up to write a strategy document and say goodbye. We get into the concrete decisions you have this week, with someone accountable and a single channel.
Deciding what to build and what not to
Half the value is in what gets dropped. We sort the list of ideas by what moves your business and we say out loud what isn't getting done yet.
Reviewing what already exists
We look at the software you were handed: how it's built, what can be sustained, what's going to cost you dearly later and what has to be fixed first.
Bringing order among vendors
We translate what you're being quoted, we ask the questions you didn't know to ask, and we put in writing what each one delivers and how it gets verified.
This page lives inside application operations and support. If what you need is to build the system, that's software development; if what's missing is hands on your team, that's dedicated technical staff.
Three ways to start
Depending on what you have on the table today
Almost nobody arrives asking for "technical direction". They arrive with one of these three things, and the work is built around it.
Nobody is running the area
Ongoing engagement: priorities, architecture decisions and the technical budget reviewed with you on a fixed rhythm.
There's a piece of software to review
A technical review with findings sorted by risk and by what they cost to fix, and by who should do each one.
There's a proposal to evaluate
We read what you were quoted, point out what's missing from the scope and tell you what to ask before you sign.
Scope
What defines the work in your case
There's no catalogue rate because no two companies have the same technical maturity. This is what we look at before proposing anything.
Which decisions are open
One platform to choose weighs differently than twenty tasks to prioritize. The rhythm of the engagement comes out of that.
What's already built and who built it
If there are vendors already at work, part of the job is understanding them before giving an opinion on what they deliver.
Who executes afterwards
We can stay only in the direction, or take charge of building and running it too. Those are two different scopes.
Who we talk to on your side
Technical direction leans on someone from the business who answers questions. Without that counterpart the decisions stall.
In the diagnostic we go through these four points, and out of it comes a proposal with the scope in writing. Book a free assessment.
Fit
When something else suits you better
You already have a technical lead with judgment
If there's someone in-house who makes these decisions and answers for them, what you may be missing is hands or a system, not direction.
You're looking for a full-time in-house hire
We work on agreed hours and remotely. If the role you need is a permanent hire on your payroll, that's a recruiting process.
Questions
What clients ask before we start
What is a fractional CTO?
Someone who takes on your company's technical direction for an agreed number of hours, without joining the payroll. They decide with you what to build, review what gets built, and answer for the technical judgment in front of your vendors.
How is it different from a one-off consulting engagement?
A consulting engagement delivers a document and leaves. Here the work is continuous: decisions come up every week and someone has to be there to make them with you. We do one-off reviews too, and in that case we call it that.
Are you going to say everything has to be rebuilt?
It's almost never the right answer and selling you a rebuild is not our business. What usually comes out of a review is what holds up as it is, what gets fixed and what only needs documenting.
Can you work with the vendor I already have?
Yes, and it's the most common case. We don't come in to displace anyone: we come in so that what they deliver can be verified. If the review shows that vendor isn't up to it, we tell you, with the reason.
How is it billed?
By an agreed monthly commitment, or by the closed scope of a review. The figure comes out of the diagnostic and is put in writing in the proposal: we don't publish a price here because it would depend on the case.
Do you work with companies outside Colombia?
Yes. We work remotely with companies in Colombia, Mexico and Panama, in the same time zone and with meetings inside the working day on both sides.
Next step
Tell us which decision is on your plate
That's enough to start: what you were proposed, what you have built and what worries you. We'll tell you whether this is right for you or whether something else is a better fit. No strings attached.
Prefer to write to us? Tell us what you need.