A project to launch, an application hitting its limits, a team to reinforce, an architecture decision to settle: each situation calls for a different kind of engagement. Hconsul brings senior engineering expertise and the working arrangement that actually fits your context — not the one that suits us.
Four situations come up in almost every first conversation. Recognize yours: it points straight at the matching solution.
Matching solutions
Your situation is not listed? That happens often. Tell us about it: the first conversation exists to qualify the need, not to sell you a format.
Each solution answers a specific difficulty and ends in identified deliverables.
The difficulties you are facing
A need stated by the business that does not translate into usable specifications. Estimates that vary threefold depending on who you ask. No way to choose between solutions for lack of a reasoned comparison.
What you get
An investment decision grounded in technical analysis rather than intuition. A scope settled before budgets are committed — that is where projects drift, far more than during development.
When to use it
Before launching a structural project. Before choosing between building, buying and integrating. When two internal teams are defending incompatible approaches.
Expected outcomes
A written scoping note, a scope broken into deliverable increments, an estimate in effort and calendar time, and the discarded options with the reasons why.
The engagement model decides who steers, who carries the risk and how you are billed. We discuss it during scoping — including when the model that fits you best is not the one that pays us most.
When it is the right call
The need is moving, the in-house team exists and steers, the duration is uncertain.
What you gain
Full flexibility on scope, direct control on your side, capacity adjusted as you go.
What we deliver
An engineer embedded in your rituals, a monthly activity report, a regular review with you.
Terms
Billed on time spent. No minimum term, fifteen days’ notice on both sides.
When it is the right call
The scope is settled, you want a firm commitment on price and date, and you do not have the capacity to steer day to day.
What you gain
A budget known upfront, the overrun risk carried by us, an obligation of result.
What we deliver
An application in production, its documentation, handover to your teams, and a correction guarantee after go-live.
Terms
Firm price on a defined scope. Anything outside it is quoted as an amendment — never as a surprise at the end.
When it is the right call
You need an outside opinion, occasionally but regularly, without committing development capacity.
What you gain
Regular access to senior expertise at a contained cost. Decisions settled quickly rather than deferred.
What we deliver
Regular sessions, written architecture decision records, availability for urgent calls.
Terms
A defined monthly volume, carried over from one month to the next.
When it is the right call
A structural decision is about to be made and you want it tested against an outside view.
What you gain
A validation or a warning before you commit, at a cost nowhere near that of correcting course later.
What we deliver
A review report with the points of concern, the alternatives examined and a reasoned recommendation.
Terms
A short engagement on a fixed scope, typically one to three weeks.
When it is the right call
You have a steady flow of needs and would rather deal with someone who already knows your system.
What you gain
No ramp-up time on each new topic. Knowledge of your technical history that compounds.
What we deliver
A named contact, reserved capacity, a quarterly review of your technical direction.
Terms
A framework agreement with negotiated terms, drawn on as needed.
Every step produces something you keep, whatever happens next.
Workshops with your business and technical teams, reading the existing code, reviewing past incidents. We look for the real problem behind the stated request.
DeliverableThe problem and its constraints, restated in writing.
Breaking the work into deliverable increments, estimating effort, identifying dependencies and risks. Discarded options are documented with their reasons.
DeliverableA costed scope, a schedule, a risk register.
Defining the target structure, the boundaries between components and the technology choices, with their trade-offs stated.
DeliverableAn architecture document and a decision log.
Two-week iterations, each closing with a demo on a real environment. Code is pushed to your repository from day one.
DeliverableA deployed, testable version at the end of every iteration.
Automated tests proportional to risk, systematic code review, static analysis wired into the build. Quality moves with development; it is not a phase.
DeliverableCoverage report, analysis results, acceptance record.
Automated deployment, a low-risk cutover strategy, close monitoring for the first days, a tested rollback procedure.
DeliverableThe application in service, operations documentation, access handed over.
Measuring what shipped — real performance, incidents, usage — and deciding what comes next on that basis.
DeliverableA measured review and recommendations for the next cycle.
Our work is on engineering problems that recur across very different settings. Here is how they take shape by industry.
Complete traceability of operations, moving regulatory requirements, high transaction volumes, and legacy systems that have to coexist with recent architectures.
Unusually complex business rule engines, contracts managed across decades, integration between underwriting, administration and claims, portfolio migrations.
Seasonal load peaks of tenfold, stock consistency across channels, real-time synchronization with logistics, availability requirements through commercial peaks.
Confidentiality and hosting of sensitive data, interoperability between heterogeneous systems, access traceability, continuous availability.
High-volume event streams, geolocation, route optimization, integration with partner systems in wildly varying formats, degraded-mode operation.
Multi-tenant architecture, scaling, exposing APIs to third parties, frequent zero-downtime deployments, data isolation between customers.
Statutory accessibility, data sovereignty, long decision cycles, extended maintenance horizons and heavy documentation duties.
Hconsul is a recently founded company. This section describes the technical stakes of these industries — it is not a client list.
We do not claim to replace a large consulting firm. For some needs one will suit you better. Here is where our format gives you more.
The company was founded by a software engineer with more than ten years on complex enterprise systems. You are not funding a learning curve on your project.
No intermediate layer, no committee to approve an architecture choice. What is decided in the morning is built in the afternoon.
Two weeks between agreement and the first day of work. Context is picked up from the real code, not from a transition document.
A reasoned technical opinion, including when it contradicts the original request. We will tell you if your project does not need the means you are considering.
The engagement adapts to your organization. We have no catalogue to move and no consultants to place.
We are not trying to become indispensable. Documentation, handover and reversibility are planned from day one.
We work mainly on the .NET ecosystem and on distributed architectures.
When your system runs on a different stack, we say so and point you elsewhere.
Each technical area is set out in detail on the Expertise pageAllow two weeks between agreement and the first day, in most cases. That covers the contract and the technical preparation. For something urgent we can start sooner if the scope is clear — we would rather tell you honestly than promise a date we cannot hold.
Describe your situation. We answer with an analysis and a first direction — not a sales brochure. You leave with our written reading of your problem, whether or not you continue with us.
Hconsul · Paris region, France · RCS Nanterre 994 546 828 · {{EMAIL_CONTACT}}