A website can help people discover your company, assess its offer and make contact. That does not mean every visit creates a new sale. A useful business case distinguishes activity from additional profit and states which assumptions remain uncertain.
Choose the Outcome Before the Design
Decide what success means: qualified enquiries, completed bookings, direct orders or less time answering recurring questions. Choose a baseline and record the current acquisition channels. Some customers who use a form would otherwise have called; counting all form revenue as new revenue would overstate the benefit.
An Illustrative Calculation
The following figures are invented planning inputs, not a QA10 customer result or price offer.
Assume a website and its first year of operation cost 12,000 PLN. It produces 10 additional qualified enquiries per month, 20% become orders, and each order contributes 600 PLN after the variable costs of fulfilling it.
Annual incremental contribution = 10 × 20% × 600 PLN × 12 = 14,400 PLN
Illustrative ROI = (14,400 − 12,000) / 12,000 × 100% = 20%
This is a simple annual model, not a cash-flow forecast. It excludes financing and tax effects. If only five enquiries are additional, contribution falls to 7,200 PLN and the illustrative ROI is −40%. The calculation is useful because the assumptions are visible, not because the example promises a particular return.
Include All Relevant Costs
Account for design and development, copywriting, photography, staff time, hosting, licences, maintenance and paid acquisition. Separate one-off costs from recurring expenses. For a longer investment horizon, model the timing of cash flows rather than treating future income as immediate cash.
Measure the Whole Journey
Track visits, meaningful actions, qualified enquiries and completed sales using a consistent definition. Connect the enquiry source to the sales process where lawful and practical. Ask the sales team about lead quality and duplicate contacts. Analytics alone cannot prove that the website caused a sale.
Use an appropriate privacy and consent setup. Compare similar periods and consider seasonality, campaigns, price changes and changes in sales capacity. A small sample can fluctuate substantially; avoid calling every short-term change an improvement.
Remove Obstacles to Action
A clear service description, readable mobile layout, accessible form and reliable contact path can make the site easier to use. Loading performance matters, but there is no universal percentage increase in sales for each second saved. Check real user experience alongside controlled tests.
Technical SEO helps search engines discover and interpret useful pages. Sitemaps, structured data and metadata do not guarantee indexing, ranking or traffic. The content must answer the visitor’s question, and the business still needs a way to reach the right audience.
Decide What to Improve Next
If traffic is low, review discovery and distribution. If visits are relevant but enquiries are weak, inspect the offer and contact journey. If enquiries do not become sales, investigate qualification and follow-up before commissioning a redesign.
Explore Q-Dev for a website built around an agreed business task. Project scope, price and schedule are set individually; the example above is not a QA10 offer.