How an engagement is shaped
Senior React and Node.js work for B2B product teams. This page states the formats, the estimate method and the limits. It does not publish a rate, a headcount or a sample invoice.
Formats we describe
A fixed scope after a written brief. Senior attention on one product, not a published bench of six to eight people. A technical audit of an existing system. Support and later development only when handover and responsibility were agreed. Discovery comes before a build contract. An estimate is returned within one business day of a usable brief.
How a price is calculated
The figure depends on scope, integrations, access to data and environments, the roles actually required and the timeline. Currency, tax treatment and expenses are stated in the proposal for that brief. There is no public hourly rate, no published minimum budget and no example month with invented hours. A request that assumes a team of six to eight inside EUR 50,000 a month cannot be confirmed from this page.
Included, and billed separately
The agreed engineering work, decision notes, and handover of code and documentation for that scope are part of the engagement. Third-party licences, hosting bills and travel are separate unless the proposal says otherwise. A change of scope is written down before the extra work starts.
Capacity on 5 November 2026
The studio describes itself as a small senior team and does not publish an exact headcount. Available capacity for a new project is confirmed in the reply to a brief, not on this page. Partners are not presented as an unnamed pool that can be switched on.
When this is a poor fit
A purchase that needs a rate card before any conversation. Round-the-clock operations cover, which is not a published standard offer. A domain where there is neither a client write-up nor a relevant engineering demo, until a scoped review says the work is still a fit. Treating simulator numbers on the demo pages as client results.