Book a call
Book a discovery session contact@pinnaclecodelabs.com

</> Discovery session

Let's map
your dots.

A 45-minute discovery session with the engineers who would do the work. Bring the thing that is stuck — we will tell you where the break is, whether or not you work with us.

What to expect

  • 0145 minutes, with the engineers who would do the work
  • 02No deck, no discovery fee, no pipeline nurture
  • 03You leave with a written map of your system
  • 04If we are not the right partner, we will say so and point you on

Other ways in

We reply within one business day

Thanks — brief received. We will come back within one business day with a first read on where your dots break.

Before you write

Questions people
ask first.

If yours is not here, ask it in the brief — we answer plainly.

How small an engagement will you take?

Discovery on its own is a valid engagement — a week or two, priced separately, ending in a written map and costed options. Plenty of relationships start and pause there.

Do you work with our existing engineers?

Often, and it is usually the better outcome. Senior engineers embed in your squads, work in your process and leave capability behind. Knowledge transfer is a deliverable, not a favour.

Who owns the code and the infrastructure?

You do, from day one. We work in your repositories and your cloud accounts. There is nothing to extract or hand back if we part ways.

What happens after launch?

Thirty days of cover are included: we fix defects in what we shipped, at no cost, no debate. After that you can retain reserved capacity or take it fully in-house with runbooks and a working session.

Can you tell us not to build something?

Yes, and we do. If configuration, a process change or an off-the-shelf tool solves it, that is the recommendation — even when it costs us the work.

How do you estimate?

Not before discovery. Once scope is real we give a range with the assumptions written next to it, then hold it. Change requests are priced openly against the same baseline.