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.
Pick a timePick a time
The calendar reflects Tomáš's real Outlook availability — any meeting on his calendar blocks the slot automatically.
1. Pick a time
Use the arrows to browse weeks that have open 30-minute slots. Times shown in Europe/Prague.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 minIntro
Brief context — who you are, what you do, what you are solving. No formalities. - 5–20 minTechnical deep-dive
You describe the problem, we ask specifics. We understand the architectural root cause, not just symptoms. - 20–30 minConcrete 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.