Choose a service
WORKING TOGETHER
You can work with me directly or, if you prefer an independent platform between us, manage the project through Contra. Either way, the scope, payment stages and responsibilities are agreed before development starts.
My Contra profile confirms my identity and provides an optional platform for contracts, funded milestones and project payments.
CHOOSE THE WORKING MODEL
For most projects, the simplest route is to agree the scope directly, sign the project agreement and follow the agreed payment milestones. You communicate with me throughout the project and payments follow the proposal rather than a generic package.
If you would rather use an independent platform for the commercial side of the project, I can set the engagement up through Contra after we agree the scope. Contra can handle the project agreement, funded milestones or escrow-based payment structure and its dispute-assistance process.
Contra and payment-processing fees may apply and are shown by Contra before payment. They are separate from my project estimate unless explicitly included in the proposal.
You do not need to discover me through Contra to use it. If we meet through By Stanislav, I can still invite you into a Contra project after the scope is agreed.
FROM IDEA TO HANDOVER
Use the calculator or contact me directly to give me the first picture of the project. The calculator is an indicative range, not a binding quotation.
I review what needs to exist, what is already available, where the uncertainty is and whether anything should be removed or split into a later phase.
You receive the agreed scope, price, payment stages, expected delivery range and the assumptions the estimate depends on.
We confirm the project terms before development starts. If you choose Contra, the project is created there with the agreed commercial structure.
The first agreed payment reserves the project and starts the work. I do not ask for the entire value of a normal custom project upfront.
You see real progress during the project. Larger builds are divided into meaningful milestones rather than disappearing into a long period of invisible work.
The final stage is reviewed against the agreed scope. Any unresolved agreed-scope issues are handled before handover.
After the agreed project balance is complete, I hand over the agreed source code, production assets, documentation and access that form part of the project.
TYPICAL PAYMENT STRUCTURE
The exact schedule is confirmed in the proposal. These are the normal starting structures I use.
Typically under £2,000
Best suited to focused landing pages, small websites and clearly defined technical work.
Typically £2,000–£8,000
This keeps the project moving while giving both sides a meaningful review point before the final balance.
Typically £8,000+
Larger web applications should not be financed as one giant upfront payment or one giant payment at the end. The milestone structure is agreed around the actual architecture and delivery plan.
Ongoing support
The exact coverage, boundaries and response expectations are defined before the maintenance period begins.
WHEN THE SCOPE ISN’T CLEAR YET
Existing systems, inherited codebases and technical rescue work can hide more uncertainty than a new build. When I cannot responsibly price the implementation from the information available, I may recommend a paid discovery or technical assessment first.
That work produces a clearer technical picture and a better implementation decision instead of turning unknown risk into an inflated fixed quote.
SCOPE CHANGES
The agreed price covers the agreed scope. If a material new feature, workflow or integration appears during the project, I will separate it from the existing scope and estimate the change before implementing it.
Small implementation details are part of normal delivery. A new marketplace, chat system, mobile application or major workflow is not a “small revision” simply because the project is already in progress.
IF A PROJECT STOPS
If a direct project is cancelled or paused, completed work and payments already due are handled according to the project agreement. Future unstarted milestones are not treated as completed work. If the project is managed through Contra, cancellation, escrow and refund handling also follow the applicable Contra project rules.
OWNERSHIP & HANDOVER
Once the agreed project payments are complete, I provide the source code, production assets, documentation and account or repository handover included in the scope.
Third-party software, fonts, APIs, hosting services and licences remain subject to their own terms. I do not pretend a project payment transfers ownership of something a third party licenses separately.
EXTERNAL SERVICES
Domain registration, hosting, paid APIs, payment-processing fees, external software licences and similar services are not silently bundled into a development estimate unless the proposal explicitly says they are included.
Where an external service is required, I will make the dependency clear before it becomes a surprise invoice.
WHY THE EXTRA OPTION EXISTS
By Stanislav shows my real products, process and identity, but a new client may still prefer a third party for the commercial relationship. That is why Contra is available as an option rather than a requirement.
Identity verified on Contra ↗You can verify the profile independently before deciding how you want to structure the project.
START WITH THE PROJECT
Build an indicative estimate or send me the project directly. If you prefer Contra, mention it when we discuss the scope and I can structure the engagement there.
View verified Contra profile ↗