Why pricing is individual
Two projects with the same short label may have very different requirements. A business website with prepared content is not equivalent to a multilingual migration with integrations. A standard online store differs from custom checkout rules, ERP synchronisation and specialised pricing. We first define what must be built, how it will be accepted and what remains outside the proposal.
Services available by individual proposal
Business website
Structure, design, content, CMS, languages, forms, SEO migration and integrations determine scope.
Learn more →Landing page
The proposal depends on message readiness, bespoke design, forms, analytics and CRM connections.
Learn more →Online store
Catalogue, checkout, payments, delivery, migration and order automation are central factors.
Learn more →Custom web application
Users, roles, business rules, files, notifications, payments, APIs and load shape technical scope.
Learn more →CRM, ERP and custom systems
Modules, processes, permissions, reporting, migration and existing system connections are assessed.
Learn more →Mobile application
Platforms, backend, offline behaviour, notifications, payments and store publication affect delivery.
Learn more →WordPress support
Website condition, plugins, custom code, backups, security and response needs determine the model.
Learn more →Laravel support
Version, code quality, tests, dependencies, infrastructure and criticality require an initial review.
Learn more →Monthly support
Task capacity, priorities, response expectations, monitoring, backups and reporting are agreed.
Learn more →Factors that shape the proposal
- Readiness and quality of the brief, content and design
- Number of roles, screens, pages and business scenarios
- Integration complexity and quality of external documentation
- Volume, format and condition of data to migrate
- Security, logging, approvals and personal-data requirements
- Load, performance, hosting and deployment process
- Automated tests, documentation and training
- Timeline, third-party dependencies and post-launch support
How a proposal is prepared
Initial enquiry
You share the objective, current problem, users and available materials.
Discovery call
We examine the workflow, constraints, integrations and success criteria.
Scope and assumptions
We document included modules, responsibilities, exclusions and dependencies.
Individual proposal
You receive an approach, stages and terms tailored to the project.
What to send
Useful material includes a link to the current site or system, a short business description, primary users, essential functionality, example documents or screens, required integrations, any fixed deadline and a contact person. A finished technical specification is not required.
Frequently asked questions
Can you price a project from a very short description?
We can explain the next steps and identify missing information. A dependable proposal requires a sufficiently clear scope.
Do you offer fixed-price delivery?
Where scope and acceptance criteria are clear, the agreed work may have a fixed price. Changes outside it are assessed separately.
Can the project be split into stages?
Yes. Custom software and larger stores often begin with a priority MVP or module.
Are paid services and licences included?
Only when explicitly stated. Hosting, licences, external APIs and advertising budgets are normally separated.
How do you estimate an inherited project?
We begin with a technical audit because version, code quality, documentation and infrastructure influence risk.
Do you provide monthly support?
Yes, after clarifying the system, expected capacity, priorities and response requirements.