Pick the one that sounds like you. The page below shows how it works, what you get, who you will work with and how to start. The other three stay on the page.
Four kinds of help. Read the one you picked, or all four.
Each one is laid out the same way, so you can compare them. Your pick, if you made one, is outlined.
No pick yet. Choose a card above, or answer the three questions further down.
Help 1 of 4 · Advice before you build
IT consulting
IT consulting helps you decide before you spend. We look at what you want to do, what you already have and what it will take. Then we tell you which technology to use, in what order, and roughly what it should cost. You can act on the advice with us, with another team, or on your own.
How it works
1Listen. A call about your goal, your team and your limits.
2Look. We read what you already have: documents, quotes, code or accounts.
3Compare. Two or three real options, and what each one takes.
4Recommend. One clear choice, a plan and a budget range, explained in person.
What you get at the end
A written decision memo: the options, our pick and why
A plan in phases, with what to build first
A budget range and a timeline for each phase
The main risks, and what to do about each
A walk-through call where you can ask anything
Full ownership of the memo and everything in it
The end of the work: a decision memoExample
The question
Should we build our booking app from scratch, or start from a ready-made tool?
Three options
AA ready-made tool, as it isFitSpeedControl
BA ready-made tool, plus custom partsFitSpeedControlOur pick
CBuild everything from scratchFitSpeedControl
Why B. It gets you live quickly and leaves room to grow. Look again once you have real users.
Plan in phases
1 Booking and payment2 Reminders3 Reports
Time and hours
Timeline in your written proposal
How you can hire us
Assessment
Who you will work with
A senior engineer who has built this kind of system. They write the memo and walk you through it.
How to start
Book an intro call. We agree the question you want answered, then send a written proposal with scope, timeline and quote. No cost until you agree.
Good fit if you are about to spend on software and want a second opinion first, or you hold several quotes and cannot compare them.
A senior engineer acts as your technical lead for part of every week. They set the technical direction, guide your developers or vendors, and speak for technology in your leadership meetings. It suits startups and small companies that need senior judgement without a full-time hire.
How it works
1Agree priorities. What the business needs from technology this quarter.
2Set the rhythm. A fixed weekly call, reviews of work in progress, and time to unblock your team.
3Review decisions. Tools, vendors, hiring, security and cost, before you commit.
4Report monthly. What moved, what is at risk and what comes next.
What you get each month
A fixed amount of senior time, set in your written proposal
A weekly call and a short written note after it
Reviews of plans and code from your developers or vendors
A technology roadmap, updated together each quarter
A monthly report: what was done, what is at risk, what is next
One week with a part-time CTOExample
MonPrioritiesCall with you
TueReviewPlans and code
WedUnblockAnswer the team
ThuDecideTools and vendors
FriNoteDone, risks, next
Once a month: the report, and a look at the roadmap.
Time and hours
Hours and weekly rhythm in your written proposal
How you can hire us
Monthly (care plan)
Who you will work with
A senior engineer as your CTO, backed by the rest of our team when the work needs more hands.
How to start
An intro call, then a short assessment of your product, team and plans. Then a written proposal with the hours, the weekly rhythm and the monthly report. No cost until you agree.
Good fit if you are a founder making technical decisions alone, or your developers have no senior person to learn from.
We look after software you already have. We fix bugs, apply updates and make small changes, so it keeps working as your business changes. Your team raises requests in one place, sees each one move through a queue, and gets a summary every month.
How it works
1Take over. We read the code, accounts and any notes, and list what we find.
2Set up the queue. One place to raise a request, with priorities we agree.
3Fix and change. Requests are worked in order. Bigger changes are quoted in writing first.
4Report monthly. Requests closed, hours used and what to plan next.
What you get each month
Bug fixes for the problems your team reports
Updates to the software and the tools it depends on
Small changes, within the hours you agree
A request queue you can see, with a status on every request
Notes and documentation kept up to date, and owned by you
A monthly report: requests closed, hours used, what to plan next
Your requests, in one queueExample
Every request has a type, a priority and a status. The reply time is agreed in your written proposal.
Checkout shows an error on some phonesBugHighBeing fixed
Update the payment libraryUpdateNormalWaiting
Add a tax number field to invoicesSmall changeNormalDone
Report export is slow on MondaysBugNormalWaiting
Change the colour of the order buttonSmall changeLowDone
Bigger changes get a written quote first. Nothing starts without your yes.
The monthly report, in shortExample
Closed this month
Checkout error, tax field, button colour
Still open
Payment library update, slow report
Hours used
Shown against the hours you agreed
We suggest next
Update the payment library
Time and hours
Monthly hours and reply times in your written proposal
How you can hire us
Monthly (care plan)
Who you will work with
A senior engineer who knows your software, backed by the team.
How to start
An intro call, then a short assessment of the code and accounts. Then a written proposal with the monthly hours and the reply times. No cost until you agree.
Good fit if your software works but nobody looks after it, or the person who built it has left.
Engineers from our team who work inside your product team. They join your chat, your task board and your code repository, follow your process, and take on the work you give them. You set the priorities. We make sure the engineers are senior and supported.
How it works
1Tell us the roles and tools. What you need built, and how your team works.
2Meet the engineers. We propose people for the roles. You meet them before you decide.
3Join your team. They get access to your tools and start with a small first task.
4Review monthly. Look at the work together, then add, swap or reduce engineers.
What you get each month
One or more engineers working in your team, for the hours in your written proposal
Work done in your tools and your process
Code in your repository, and accounts in your company's name
A lead on our side you can call when something needs a decision
A monthly review of progress and of how the team fits
Two engineers join your setupExample
Your team
YouProduct owner
Your developerAlready in the team
Your designerAlready in the team
From Supervention
Engineer 1Senior
Engineer 2Senior
Together, in your tools
Your chat
Your task board
Your code repository
Your daily stand-up
Your release steps
They work in your tools and follow your process. The code and the accounts stay yours.
Time and hours
Engineers, hours and start date in your written proposal
How you can hire us
Monthly (dedicated developers)
Who you will work with
Senior engineers from our team, with one lead on our side. Their names and roles are shared before you agree.
How to start
An intro call, a short look at your team and tools, then a written proposal with the number of engineers, the hours and the start date. No cost until you agree.
Good fit if your plan is clear but your team is too small to deliver it, and you do not want to hire permanently yet.
No prices here. Every option starts with a written proposal. Select one of the four to light it up.
Compare
Commitment
One short, fixed piece of work. It ends with a written memo.
Monthly. Fixed hours and a weekly rhythm, set in your written proposal.
Monthly. Agreed hours for fixes and changes, set in your written proposal.
Monthly, for each engineer, with the hours set in your written proposal.
Best for
Choosing technology, a plan or a vendor before you spend
Founders and small teams that need a senior technical lead
Live software that needs fixes, updates and small changes
Teams with a clear plan and too few engineers
What you walk away with
A decision memo, a phased plan and a budget range
Clear technical direction, reviewed decisions and a roadmap
Software that keeps working, and a record of every change
More delivered by your team, in your repository, owned by you
Nothing lit up yet. Select one of the four to light it up.
Which one for me?
Three questions. We suggest one. Nothing is sent anywhere, and you can still read all four.
1Where is your software today?
2What is missing most?
3How long do you need the help?
Your suggestion
Answer the three questions.
0 of 3 answered. We show one suggestion, and a second one if it is close.
A real person, a real profile
The person you will talk to.
Supervention is a new company, and we will not make up logos or reviews. You get the person instead, and a profile you can check yourself.
You can ask us on the first call: which of the four fits and which does not, what we would do first in your place, and who exactly will do the work.
Years building software
10+ years, by the founder’s own count
Upwork profile
Top Rated Plus · 100% Job SuccessHis own record, not the company’s: 5,347 hours across 9 jobs (6 completed, 3 in progress), as of October 2026. Three finished contracts, rated 4.8, 5.0 and 5.0.Open the profile: Arun V.
Your first message
A person reads it and replies within 1 working day
How the work runs on this line
From the first call to the monthly review.
Four steps to start, then a review every month. Each step ends with something you can hold.
1
Intro call
We listen to what you need and what you already have.
You receiveA short written summary of what we heard.
2
Assessment
We look at your product, code, accounts, team or plans, whichever applies.
You receiveA findings note: what is sound, what is risky.
3
Plan
We write down what we will do, and how.
You receiveA written proposal with scope, timeline and quote. No cost until you agree.
4
Start
Access, introductions and the first tasks.
You receiveAccess in your company's name, and a plan for week one.
Then, every month: the review
We sit down with you, look at what was done and what comes next, and change the plan if it needs changing.
You receiveA plain report: what was done, hours used, what is next, and what to change.
Pick a kind of help: choose a card at the top, and this line shows how the monthly review works for it.
What you own, and what we need from you.
You own
The code, the accounts and the documentation, in your company's name
Every memo, plan and report we write for you
Your data, and every account we set up for you
30 days of free fixes after any build work we deliver
An NDA, on request
We need from you
1One person who can decide, for a short time each week
2Access to what we will work on: code, hosting and tool accounts in your name, or your plans and documents
3Honest information about what is broken, risky or unfinished
4One place to send requests, and a named person who approves the work
5A slot for the monthly review
Three ways to hire us on this line.
Every option starts with a written proposal with scope, timeline and quote. No cost until you agree.
Assessment
A short, fixed piece of work that ends in a written recommendation, so you know what to do before you spend.
Used for: IT consulting.
Monthly care plan
An agreed number of hours each month, one place to ask for work, and a plain report at the end of the month.
Used for: CTO as a service and application maintenance.
Dedicated developers
Engineers from our team who work inside your product team, in your tools. Each month you review the work and can change the team. The notice period is agreed in writing before we start.
Used for: dedicated developers.
Questions
Did not find your answer? Ask us in the form below.
Can you work inside our tools and process?
Yes. Dedicated developers, and the part-time CTO, work in your chat, your task board and your code repository, and follow your process. Accounts stay in your company's name, so you stay in control of access.
What if we only need a few hours?
Tell us on the first call. If you need one decision, IT consulting is a short, fixed piece of work, not a monthly plan. For the monthly options, the number of hours is written in the proposal before you agree.
Can you take over from another developer?
Yes. We start with a short look at the code, the accounts and any notes the last developer left. You get a written note of what we found, and what we suggest, before anything is changed.
Who is on call when something breaks?
Who is on call, at what hours, and how fast we reply are written in your proposal before we start. Monitoring and uptime for your hosting is a separate service, Managed hosting under Cloud and DevOps.
How do we end the arrangement?
Monthly arrangements end with written notice, and the notice period is agreed in your proposal before we start. You already own the code, the accounts and the documentation, so the next person can carry on.
Do you work with our existing team?
Yes. Your developers, your designer or another vendor can stay where they are. The plan names who decides what. A part-time CTO or a dedicated engineer works with them, and does not replace them unless you ask.