Let us take 30 minutes.
A direct technical conversation with a senior architect. No sales process, no pressure, no follow-up "can I call you back?" calls.
Or send an email:
info@codedock.comOpens in a new window (Microsoft Bookings)
Why 30 minutes is worth it
Fast decision
30 minutes is enough to tell whether we can help. If we can't, you'll hear it straight away — no stringing along.
Technically specific
You talk directly to a senior architect, not a salesperson. We get the problem in the first minute.
Zero commitment
After the call you get concrete recommendations. Whether we move forward is your call, not ours.
What happens on the call
0–5 min
Intro
Brief context — who you are, what you do, what you are solving. No formalities.
5–20 min
Technical deep-dive
You describe the problem, we ask specifics. We understand the architectural root cause, not just symptoms.
20–30 min
Concrete next steps
Real recommendations — tech stack, architecture, rough scope. Whether we continue is up to you.
What you get after the call
Written notes within 48 hours
A short email with key points, recommended architecture and effort estimate. Usable even if you end up working with someone else.
Transparent availability
If there is a fit, we propose a timeline — most projects start within 1–2 weeks. If not, we tell you on the spot.
Pick a time that works
The calendar reflects Tomáš's real Outlook availability. Any meeting on his calendar automatically blocks the slot — nothing manual.
Opens in a new window (Microsoft Bookings)