Book your first call.
Tell us what is stuck and we tell you what we see.
Thirty minutes, no cost. We tell you what we would do and whether this is for us. No deck and no service catalogue.
We do not close a price or a timeline on the call: first we understand the situation.
Half an hour, one question behind it
You tell us the situation and we ask questions. No deck, no service catalogue, and no pricing talk on that call.
At the end, one of three things: we tell you what we would do and we agree to work together; we tell you what we would do and you do not need us to do it; or we tell you this is not our field, and where to look instead.
If we need to look deeper, we tell you what information we need to prepare a bounded, written proposal. That is work, and it does not begin until you approve it.
What is included
The call (30 minutes, no cost)
- You tell us the situation. We ask whatever we need to understand it.
- We tell you what we see from the outside, and what would worry us if it were our project.
- We tell you whether this is a technical, an operational or a decision blockage.
- We tell you whether we can help, how, and what we would do first.
- If we cannot help you, we say so on that call, and if we know someone who can, we say that too.
If we decide to continue (bounded review, quoted)
- Read access to the code, the tickets and whatever documentation exists.
- Conversations with the key people: business, technical team, supplier.
- A review of the contracted scope and the current estimates.
- A short report: what is happening, what is blocked, what we would do and in what order.
- A meeting to walk you through it and answer anything you need.
What happens when you send the form
- 01
We read it. No commercial filter, no qualification team. It lands in our inbox and we read it.
- 02
We reply within 24 hours. With one of two answers: we propose times to talk, or we tell you we are not who you need and why.
- 03
We talk for 30 minutes. Video call or phone. No presentation, no slides.
- 04
When we hang up, you know where you stand. What we think is happening, what we would do, and who should do it.
- 05
If there is a next step, we tell you what we need in order to quote it. The proposal arrives in writing, with scope, timeline and price, before anything begins.
There is no automated email sequence, no follow-up call three days later, and no newsletter we sign you up to without telling you.
Tell us what is stuck
Four required fields. The rest, if you fill them in, help us prepare the call instead of spending it getting context.
If you would rather write before filling anything in: hola@dikeit.com · We read it ourselves.
And if you already know what you need and just want to talk: book a slot directly in our calendar.
How the scope gets defined
On the first call we do not close a price or a timeline. We have not seen the project, and estimating without having seen it would not be serious: what a rescue, a due diligence or external technical leadership costs depends on the real state of the system, on what access exists, on how many suppliers are involved, on what documentation there is, and on how urgent it is.
- 01
A first call to understand the situation
Thirty minutes, no cost. You tell us what is going on, we ask questions, and we come out knowing whether we can help and what kind of work fits.
- 02
If it fits, an initial review of the context
We take a first look at whatever exists: documentation, access, contracts, who is involved. This is where the real size of the problem becomes visible.
- 03
Definition of the scope
What is in, what is out, what dependencies exist and what can be left aside without the work losing its point.
- 04
A written proposal
With scope, price, timeline and deliverables. No open ranges: a proposal you can compare and defend.
- 05
We start only if we both approve it
If the proposal does not convince you, no harm done and you have paid nothing. If it does not convince us, we say so first.
We would rather look careful than look fast. A quote given in thirty minutes, without having looked at anything, gets broken by week three.
The fine print
What is not included
- It is not a full technical audit.
- We are not going to review your code line by line, run a security analysis or do load testing. If that is needed, we will tell you, and it is a separate job.
- It is not a due diligence.
- If you are weighing an investment or an acquisition and need a report that holds up in front of an investor or a board, that is a technical due diligence: another level of depth and another engagement.
- It is not a sales proposal.
- On the call we are not going to present services or rates. If there is something to propose, it is proposed afterwards and in writing.
- It is not an estimate for your project.
- We cannot tell you in 30 minutes what it costs to finish something we have not seen. Anyone who does is making it up.
- It is not a second opinion on a decision already made.
- If the goal is for us to endorse something already signed, the conversation is no use to anyone.
Who it is for
- For whoever has to decide, not for whoever has to execute.
- For anyone who has already invested in a digital project and does not know whether it still makes sense.
- For anyone with a technical supplier who needs someone that understands what they are being told.
- For anyone about to sign something expensive who wants an independent read first.
- For companies with a real, working business and a digital side that is not keeping up.
Who it is not for
- Not for sourcing a development quote. We do not build to order.
- Not for comparing supplier prices. We do not bid against your agency.
- Not for project ideas that have not started. With nothing built, there is no situation to diagnose.
- The call costs nothing because it also helps us decide whether this is a project we want to take on.