Fixed price
A written scope, a milestone plan and one total. Best when the requirements can be defined and the main risk is scope creep rather than uncertainty.
PricingHow projects are quoted, what a quote includes, and why there is no price list
Every project here is quoted per scope. You get a written scope, a milestone plan, a timeline and one total before work starts. Fixed price suits a defined build; hourly suits unpredictable changes; a retainer suits ongoing support. Nothing is billed beyond the agreed scope without approval first.
The question behind most pricing searches is not "what is the number" but "am I about to be overcharged". That is answered by seeing the scope, the exclusions and the payment schedule in writing - not by a table of invented ranges.
For a buyer comparing quotes and trying to work out what is actually included in each one.
24h
Reply to an enquiry
0
Hidden line items
100+
Projects quoted and delivered
Three ways to engage
The model is chosen to fit the work, not to maximise the invoice. Each has a clear place.
Hourly
For audits, debugging, small changes or a project where the next step genuinely depends on what is found. Hours are logged and shared, with a cap agreed in advance.
Monthly retainer
A defined support scope or block of hours each month. Sensible after launch, or for a product that changes continuously and needs a predictable cost.
Mixed
A fixed price for the build and a retainer for support is common. The two are quoted separately so you can stop one without renegotiating the other.
What every quote includes
If a quote is missing any of these, it is an estimate. Ask for the missing parts before comparing totals.
A page-by-page or feature-by-feature scope, in writing.
The full price, with payment stages tied to delivered work.
A timeline with milestones, not only an end date.
The design revision rounds included, and what happens after them.
Hosting, domain, analytics and search indexing setup.
A handover walkthrough and a written support window.
What is explicitly excluded, so it cannot appear later as a surprise.
Why there is no price list on this page
A price list requires a fixed assumption about scope. The same five-page brief can mean a simple brochure site or a site with a booking system, three languages and a payment gateway. Publishing one number would either mislead the small project or lose the large one - and it would be wrong for almost everyone.
What can be published honestly is the structure: what is included, what is excluded, how payment is staged and how long each kind of project takes. That is enough to compare two quotes properly, which is the real goal.
If a fixed budget is the constraint, say so at the start. The honest response is either a smaller scope that fits it or a clear statement that it does not. What will not happen is a low quote that grows through change requests after the work has begun.
What to send for a quote
A paragraph about the business, the pages or features you think you need, any existing site, and the deadline if there is one. A budget range is helpful but optional. The reply is a written scope and price, free and with no obligation.
What changes the number
These are the factors that move a quote up or down. They are discussed before the price is written, not discovered during the build.
How defined the scope is
A clear list of pages and features can be priced tightly. A vague brief attracts a higher number because the unknown has to be priced in.
How much is built already
An existing brand, content and photography reduce work. A rebuild on a broken platform adds audit and migration time before anything new is built.
Integrations and data
Payments, shipping, accounting, SMS and existing systems each need handling and testing. Large catalogues need import, validation and an admin process.
Timeline and availability
A deadline that requires displacing other work costs more. A project that fits the queue does not. The difference is stated, not hidden.
Typical timeline
- Landing page or one-page site
- About 1 week
- Business website, 5 to 10 pages
- 2 to 3 weeks
- E-commerce store with payments
- 4 to 8 weeks
- Custom web application or dashboard
- 6 to 12 weeks
- Cross-platform mobile app
- 6 to 10 weeks
Every quote is written for the project in front of me. You get the scope, the milestones, the timeline and the full price before work starts - no hourly surprises and no hidden line items. Send your requirements and the quote comes back free, with no obligation to proceed.
Frequently asked questions
From the scope. The pages, features, integrations and content are listed first, then the design, build, testing and launch work is estimated against that list. The result is one written total with milestones, not an hourly guess.
When the next step genuinely depends on what is found: an audit, a rescue of a broken site, debugging an unfamiliar codebase, or a product where requirements will change weekly. Hourly with a cap protects both sides in those cases.
The exclusions are listed explicitly. Common ones are content writing, photography, paid plugins or platform subscriptions, domain and hosting renewals, payment gateway transaction fees, and work beyond the agreed revision rounds. Each can be added and quoted separately.
Yes. Payment is staged against delivered work, with the first stage due before the build starts. The schedule is in the proposal, so the amount and timing are agreed before anything begins rather than negotiated at the end.
Yes, and it is handled in writing. A change is priced and approved before it is built, so the total only moves when you have agreed to the reason. Work is not silently absorbed or silently invoiced.
If the delay is caused by the build, it is absorbed. If it is caused by late content, changing requirements or unavailable approvals, the effect on the timeline is stated when it happens. The proposal names what each side is responsible for.
[email protected] or WhatsApp +91 63834 17749. Requirements-ai anuppunga - written scope and quote free-a kudukkurom.