A workflow adapted to the business
The application is designed around your users, data and real decisions, not around how a generic tool expects you to work.
Back to services
Freelance service
IT advisory
Help deciding what to build, which technology to use, how much scope it needs and where to start.
- Free initial assessment An initial conversation to clarify the most useful next step.
- Direct communication You speak with the person analysing and building the work.
- Clear ownership Code, accounts, access and handover are defined.
Problem and outcome
Which decision should IT advisory unblock?
The scope is built around a real problem and a verifiable outcome, not a generic list of tasks.
Problems it solves
Off-the-shelf tools do not fit the workflow, but a large product build would be too much for the current stage.A custom web application makes sense when your workflow, product or internal process does not fit well inside an off-the-shelf tool.
The goal is not to build a huge platform from day one. It is to create a useful first version with the screens, data, permissions, backend and integrations needed to validate the real workflow.
A base ready to grow
I define boundaries, models and contracts carefully so the first version can evolve without becoming debt from the start.
Lower product risk
We start with a small, verifiable version so you can learn before investing in extra modules, roles or automation.
Decisions before investment
What must be clear before choosing technology or a supplier
Useful advisory work ends with decisions and boundaries, not a list of possible tools.
Signs of a poor decision
- Starting with technology before defining the problem and users.
- Accepting an estimate that does not separate scope, risk and dependencies.
- Treating a quick demonstration as an operable solution.
What should be clear at the end
- Documented problem, priority and constraints.
- Options compared by cost, risk and maintenance.
- A bounded next step with a validation rule.
Guide price
What changes the scope of a technical review?
Three ways to start depending on the size of the need. Prices are indicative and final scope is agreed after the initial assessment.
One-off consultation
A session to structure a technical decision before committing budget.
From
€120
+ VATWhat is included
- Preparation from the context provided.
- A session focused on one decision.
- Summary of options, risks and the next step.
Boundary: This is not a deep audit or a fixed development quote.
Book a consultationAdvisory block
The most common optionSeveral sessions and technical review to define an initiative in more detail.
From
€450
+ VATWhat is included
- Map of the problem and constraints.
- Comparison of viable options.
- Initial scope and acceptance criteria.
- Final review with recommendations.
Boundary: Implementation is not included unless quoted separately.
Request an advisory blockMonthly advisory
Recurring space to resolve questions and review decisions before execution.
From
€99 /month
+ VATWhat is included
- Prepared monthly session.
- Short review of proposals or changes.
- Follow-up of open decisions.
Boundary: This does not include daily direction or unlimited implementation.
Ask about monthly advisoryService scope
Which inputs and deliverables belong in the advisory work?
Final pricing depends on scope, integrations and project state. If it does not fit, I will say so before estimating.
Work included according to scope
- Authenticated dashboards, forms, workflows and data views.
- Backend APIs, databases and integrations when the app needs them.
- Admin areas for managing content, users or operational records.
- Deployment, environment notes and a maintainable project structure.
Boundaries we put in writing
- This is not a deep audit or a fixed development quote.
- Implementation is not included unless quoted separately.
- This does not include daily direction or unlimited implementation.
Process
How I turn uncertainty into a testable decision
I have full-stack and backend depth, so I can connect interface, data, APIs and deployment without splitting the problem into silos.
-
Map the workflow, users, permissions and data that matter first.
-
Define a small first version that can be built and validated.
-
Build iteratively with clear interfaces between frontend and backend.
-
Validate the critical paths and leave the codebase ready to evolve.
Related proof
Technical judgement applied to real systems
I write about backend work, tools, automation and practical decisions while building software.
Related article
Read technical notes
I write about backend work, tools, automation and practical decisions while building software.
Go to blogDecision guide
Get technical judgement before you invest
Review scope, suppliers, architecture and priorities before committing budget to a technology project.
FAQ
Questions before requesting a technical second opinion
Can you build both frontend and backend?
Yes. My strongest base is backend, and I can work across the full stack when that helps ship a useful product.
Do you build large platforms?
I prefer starting with a focused version. If the scope is large, I help split it into realistic phases.
Contact
Does this fit your project?
Tell me what you want to build, what you have now and what outcome you need. If it fits, I’ll suggest a clear next step.