Free or paid website: avoid discovering the limits too late
A free website can help you test an idea and publish basic information. A paid solution is justified when it adds necessary capabilities, support or terms you can verify. Choose according to the task your customer needs to complete and the work you will have afterwards. A plan with no monthly fee may require your time; a paid plan may still have limits. This guide helps you compare both using the same test page.
By the end, you can:
- Test the limits of a free option
- Compare costs and terms over the same period
- Decide when it is worth changing solutions
Define a task that lets you compare the options
Write one sentence describing the outcome the visitor needs: understanding a service, checking opening hours or submitting an enquiry with three pieces of information. Prepare the same title, photograph and contact details for both solutions. Comparing a finished demonstration with an empty free account mainly measures how the examples were prepared, rather than what the tools can do.
Choose a maintenance task too. It might be changing the opening hours for a public holiday and then restoring the previous hours. Time the work only as an internal observation, including signing in, making the change, publishing and checking it on a mobile phone. If someone else will need to make the change, repeat the task with that person. Independence depends on who will do the work, the access they receive and the documentation available.
Check what free means for this service
Google Sites documentation explains how to publish and choose a website’s visibility. Use an account suitable for the business, create a test page and open the address without signing in. Check whether the information is public and the contact method works. A page that only its owner can open does not yet meet the business need.
Read the current terms of your chosen tool. Note the included address, provider advertising, storage space, editing permissions, forms, version history and usage limits. Distinguish a permanent free plan from a trial period and from an offer that requires a later contract. Do not assume that other features, such as payments or a custom domain, come with basic publishing. Save the information you checked, with the date and a link to the plan.
Compare capability, continuity and cost
Complete one row for each capability and ask for a demonstration of anything essential. The cost of an option includes building it, recurring services, changes and internal work. Use the same time horizon. Domain and email costs may be charged separately, even when the editor is described as free.
A feature being available through a plugin or integration does not mean it is included, configured and maintained. Ask who is responsible if it stops working and how much it costs to add. Paid options should be assessed with the same care. Consult Lyntev’s current pricing when including it in the comparison; the figures for this exercise should come from actual proposals.
| Check | Free option | Paid option |
|---|---|---|
| Publishing and address | Open without signing in; identify the subdomain | Confirm domain ownership and renewal |
| Contact | Send a test enquiry and confirm its destination | Repeat the test and check how it is followed up |
| Content changes | Make the change with the person who will edit the site | Confirm their independence or the scope of the management service |
| Leaving | Export the content and retain the originals | Ask for files, formats and transition terms |
Fictional scenario: a bicycle repair shop
A fictional bicycle repair shop wants to advertise repairs and receive requests for an assessment. In the first week it publishes its services, opening hours and a contact address free of charge. The team discovers that customers always ask about bicycle size and the type of fault. Before changing plans, it tries explaining those questions on the page and showing how to send the information.
Later, the shop needs to organise enquiries with photographs and confirmation of receipt. The decision then depends on that journey and who is responsible for follow-up. The team compares keeping the page, connecting a separate tool or commissioning a solution that brings the process together. It does not attribute an increase in sales to the first visits. The example shows a sequence of decisions; it does not represent a client, an implementation timeframe or a Lyntev result.
Test how you would leave before relying on the platform
Keep text, photographs and permissions outside the editor, in a company folder. Try exporting the page or content. On WordPress.com, a content export does not necessarily provide a complete copy of the design, plugins and image files. This distinction shows why you should inspect the exported file rather than simply accept that an export button exists.
Check how a new provider could use that export. A readable copy may reduce editorial work without allowing the whole interface to be reproduced. If the address depends on the provider, consider what will happen to printed links, social profiles and customers’ bookmarks when you leave. A domain the company can manage may help continuity, but it remains subject to registration, renewal and the applicable terms.
Recognise the signs that justify investment
There is a stronger case for change when a limitation repeatedly prevents an important task: enquiries do not arrive, information cannot be organised or the team spends too much effort on manual operations. Record examples and how often they occur. The number of pages, the platform’s reputation or simply having a competitor with a website does not replace this observation.
Avoid committing because you fear missing a promotion or because a demonstration looks professional. Ask for the complete contact journey, the list of costs and the exit procedure. Before payment, define what will allow you to accept the delivery. If the free solution meets the current objective, keep it and plan to review it when the business changes. If it fails an essential requirement, compare fixing it with the alternatives.
- The page opens from a link shared with someone who has no account.
- The test enquiry reaches the team and receives a clear acknowledgement.
- The responsible person can update the information or knows how to request a change.
- Recurring costs, limitations and exit terms are documented.
Record the decision and arrange a review
Use the worksheet to make the choice reversible. Record what you do not yet need to buy and the condition that would justify doing so. Set a review date or identify a specific event, such as starting to sell products. This helps avoid paying in advance for capabilities you never use and keeping a limitation after it starts to harm customer service.
Keep simple evidence: the public address, a copy of the page, the test message received and a summary of the terms checked. Do not put passwords in the shared worksheet. If you request proposals, send the same set of requirements to every provider. The comparison is clearer when each proposal addresses the same work and explicitly describes what will be left for a later stage.
Worksheet for your project
Decision: free or paid website Visitor’s task: Task for the person responsible for updates: Tools and plans compared, with date: Address and ownership: Test enquiry and confirmed destination: Essential limitation found: Initial and recurring costs over the same period: What the export actually contains: Condition that would justify changing: Responsible person and review point:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
