Skip to content
← All services

000 / Consultation

Discovery Call & Architecture Consultation

30 minutes or one hour on the phone, workflow analysis, feasibility check, architecture recommendation. You get a cost estimate for the implementation and a written summary. Book a project afterwards and the call price gets fully credited against it.

001 / Deliverables

What you get

Four concrete things you walk away with, even if you decide against a follow-up project.

Written summary

What we discussed, what your options are, which one I'd recommend for your case. By email within 24 h of the call, even if you don't proceed.

Feasibility assessment

Straight answer: is what you have in mind technically realistic and stable to build? If not, I tell you in the call, before you invest time or money.

Architecture recommendation

Which tools fit your case (e.g. Python + Docker, FastAPI, Playwright, scraping vs. APIs). So you don't build a fragile system that has to be rebuilt in three months.

Realistic cost estimate

If a follow-up project makes sense: range plus assumptions. No surprises later, no bait-and-switch.

002 / How it runs

How the call runs

  1. 01

    Inquiry

    You send a short inquiry with the question or problem. Reply within 24 h, with a proposed time and a hint about which tier (30 or 60 min) makes sense.

  2. 02

    Optional prep

    Send material ahead, code repo, screenshots, an existing tool, and I look at it before the call. Makes the minutes count more, no surcharge.

  3. 03

    The call

    30 or 60 minutes, depending on the chosen tier. Live (video or audio) or async (audio messages plus notes, if time zones are tricky).

  4. 04

    Summary

    Within 24 h after the call: written summary, architecture recommendation, cost estimate where applicable. By email.

003 / Price

Two lengths, one price per minute

Two options depending on complexity: 30 minutes for €75, 60 minutes for €150. Both tiers include prep, the call, and the written summary.

If you book a project with me after the call, the call price gets fully credited against the project. Effectively you pay nothing extra for the consultation, you only pay the filter, in case it doesn't turn into a booking.

Discovery Call

from €75 net

30 or 60 minutes · live or async

  • 30 minutes · €75, compact overview, architecture recommendation
  • 60 minutes · €150, deeper analysis, live screen-sharing
  • Workflow analysis: what makes sense to automate, and what doesn't
  • Written summary + cost estimate for the implementation
  • Call price fully credited against any follow-up project
Send inquiry

Reply within 24 h

005 / Frequent questions

What you should know about the call

Why not a free call?

Because a good call needs preparation, reading code, weighing options, sketching architecture. Plus, the price filters out inquiries where nobody really wants to invest. Result: a call that delivers something, not a 15-minute sales pitch.

And if you say it's not feasible?

Then you have the written summary with reasoning and save yourself a project that wouldn't have worked. That's the most common "worst case", and the call still paid off.

When are 30 minutes enough, when do I need 60?

30 work if you already have a concrete question ("Should I use X or Y?"). 60 is useful for more complex workflows or if we want to look at live code together.

How does the project credit work?

The call price shows up in the project invoice as "already paid". You pay the project fixed price minus €75 (or €150). Credit applies to any follow-up project with me.

Does async work?

Yes. Audio messages and shared notes, if live calls are tricky. Same price, same deliverable.

What if the call overruns?

5–10 minutes of buffer are planned. If it needs more: either schedule a follow-up, or upgrade to the 60-minute tier on the spot, you pay the difference, nothing twice.

A question, a problem, an idea?

Send a short inquiry, within 24 h you get proposed times and a few targeted prep questions.

Send inquiry