What we consult on
Code and architecture
A read of the codebase you actually have: structure, dependencies, test coverage, and the parts that will not survive the next hire or the next feature.
Infrastructure
What runs where, what it costs, what happens when it falls over, and whether the shape of it still matches the size of the business.
Cloud, AWS, and DevOps
Account and network structure, IAM, pipelines, monitoring, backup and restore. Whether your deployments are repeatable and whether anyone could rebuild the environment from scratch.
Operations and automation
The manual processes your team runs by hand, which of them are worth automating, and what the honest saving looks like once you subtract the build.
This is not the discovery call
Two different things, and it is worth being clear about which one you are booking.
Everyone starts with the discovery call. If a paid consultation is not the right thing for you, we will say so on that call rather than sell you one.
Why the consultation is paid work.
A free proposal is written to win the work. That is its only job. So it takes your description of the problem at face value, prices what you asked for, and stays quiet about anything that would make the number bigger or the timeline longer.
Nobody is being dishonest. There is simply no budget to investigate before the contract is signed, so the investigation happens afterwards, during the build, at your cost. That is where scope creep, missed integrations, and the rebuild in month four come from.
Paying for the diagnosis changes the incentive. We get paid to tell you what is actually wrong, including when the answer is smaller, cheaper, or somebody else's job.
What the consultation covers
- 01The problem in your words, restated in ours, until both match
- 02Your current stack: what runs where, what it costs, what breaks
- 03The data: where it lives, how many copies of it exist, who retypes it
- 04The commercial picture: which number this work is supposed to move
- 05Constraints we have to design around, including team, budget, and timeline
- 06Where the real risk sits, and what happens if you do nothing
What you walk away with
- A written recommendation, specific enough to act on
- A scope and a realistic range for cost and duration
- The options we rejected, and why we rejected them
- A document you own, useful even if you never hire us
- An honest answer, including if the answer is that you don't need us yet
Fee and duration
The fee is fixed and agreed before we start, so the cost is never a surprise and never depends on what we find.
If you go ahead with the project, the fee is credited in full against it. If you don't, you keep the document and owe us nothing further.
Common questions
What is the difference between the discovery call and the technical consultation?
The discovery call is free. It is a short conversation where you describe what is not working and we work out whether we can help. The technical consultation is a paid, fixed-fee engagement where we go into the code, the infrastructure, and the numbers, and give you a written recommendation you own. Everyone starts with the discovery call.
What does a technical consultation cost?
The fee is fixed and agreed before we start, so it never depends on what we find. If you go ahead with the project afterwards, the fee is credited in full against it. If you do not, you keep the written recommendation and owe nothing further.
What do we actually get at the end of it?
A written recommendation specific enough to act on: the problem restated accurately, a scope with a realistic range for cost and duration, the options we rejected and why, and an honest answer about whether the work is worth doing at all. The document is yours and stays useful even if you never hire us.
We already have a development team. Is this still useful?
Often more useful. A consultation with an in-house team is usually about architecture decisions, cloud and deployment practice, or an outside read on whether a plan holds up. We are not there to replace your engineers, and we will say so if the honest answer is that your team can handle it.
Do you work with clients outside Lebanon?
Yes. We are based in Beirut and work with clients across Lebanon and the wider MENA region, including the Gulf. Consultations are run remotely unless you would rather meet in person in Beirut.
What technologies do you work in?
We are not tied to a stack. We build with Next.js, React, Angular, Node.js, Python, Go, .NET, Laravel, PostgreSQL, MongoDB, Redis, Docker, AWS, and PyTorch, and we implement Odoo, Shopify, and WordPress. We pick the language and architecture that fit the problem, your team, and the ten-year cost.