00Book
Book a conversation
Choose what you want to talk about. Each conversation has its own context, so we both arrive prepared.
To discuss a project
A first conversation to understand what you need. Scope and cost come later, in writing.
Booking: Discuss a project
- Tool
- Cal.com, in a new tab
- Length
- Not set
- Status
- Not available yet
Online booking is not available yet
There is no published calendar for this conversation yet.
In the meantime, you can write to us.
You arrived with this context
- Service
- Consulting and architecture
It is indicative. We confirm it with you in the conversation.
Clear the contextWhat to bring
- The need or the technical challenge, in your own words.
- The service you are interested in, if you already know.
- The engagement model you have in mind, if any.
- A short context: what exists today and when you need it.
To explore a diagnosis
We talk about your case to see whether a diagnosis makes sense and what it would review.
Booking: Explore a technical diagnostic
- Tool
- Cal.com, in a new tab
- Length
- Not set
- Status
- Not available yet
Online booking is not available yet
There is no published calendar for this conversation yet.
In the meantime, you can write to us.
This call is a conversation about the diagnosis. It is not the diagnosis itself or a free assessment.
- Duration
- 1–2 weeksIndicative: we set it in writing before we start.
- Your time
- 1–2 meetingsPlus read access to what already exists.
- You get
- A diagnosis document
- Fee
- Depends on the scopeCredited against the proposal if you go ahead with the project.
Typical diagnosis questions
Each diagnosis is adjusted to your case; these are the starting areas.
- Goal
- What the system has to achieve, and for whom.
- Which constraints apply: deadlines, budget, team, regulation.
- Current state
- What exists today: code, infrastructure, integrations and documentation.
- Whose name the repository, domain, hosting and access are in.
- Risks
- What could fail or block the project.
- What depends on a single person or a single supplier.
- Options
- Which paths exist and what each one involves.
- Which one we recommend, and why.
What to have at hand
- The decision you have to make, and by when.
- What already exists: code, infrastructure, suppliers or a proposal.
- Who knows the problem and the system.
To discuss a partnership
A conversation between teams to see how we would work together on your clients’ projects.
Booking: Discuss a partnership
- Tool
- Cal.com, in a new tab
- Length
- Not set
- Status
- Not available yet
Online booking is not available yet
There is no published calendar for this conversation yet.
In the meantime, you can write to us.
If the project is your own rather than a client’s, choose “Discuss a project”.
Your clients’ projects are handled confidentially.
What to tell us
- What kind of agency or partner you are.
- The collaboration you have in mind: development for your clients, maintenance or something else.
- The technical capabilities you need from us.
- The context: timing, and whether you need white label or want to show the work in your portfolio.