Use the trial to answer a practical question: can this product run your project comfortably and make its daily management easier? A successful trial should include the real functions your visitors and team depend on, not just a check that the homepage opens. Start with a manageable test site or an agreed copy of your existing website.
IN THIS ARTICLE
01 Test the tools and customer functions for your product
- Web Hosting. For Web Hosting, explore the Account Manager, confirm cPanel access where included, upload a small test site and check the database or application environment you intend to use. If email is part of your project, verify the available mailbox tools and the correct domain setup before testing delivery. Review resource measurements after normal activity so you can see whether the selected package is a reasonable fit.
- NabWP Managed WordPress. For NabWP, open the WordPress Manager and inspect the tools available for your site. Try creating or improving one page, editing the result in WordPress, checking plugin and theme management, and reviewing available backup, staging, security and performance tools. A store should also test product pages, basket behaviour, checkout, order notifications and the payment provider's approved test mode before accepting real orders.
02 Try one focused AI Engineer task
Try the relevant AI Engineer with a specific, low-impact task. Ask it to inspect something, explain its findings and propose a small improvement. Review the action and verify the outcome yourself. The daily credits help you explore the workflow, but a complex task can use more than one AI request.
03 Keep a checklist and decide before expiry
Keep a short checklist of what worked, what remains unclear and any requirements you could not test. Contact us while the trial is active if a missing feature or error blocks your assessment. Before the end date, save your work and review the continuation details so a trial expiry does not interrupt an important launch.
04 Example: use the trial as a customer-journey test
Your trial site is a small service-business website. Write down the result a visitor should receive before testing, so the decision is based on evidence rather than appearance alone.
| Test | Expected result |
|---|---|
| Open the homepage on a phone. | Text and navigation remain usable. |
| Submit a controlled contact enquiry. | A confirmation appears and the team receives it. |
| Sign in as the website administrator. | The normal editing task works. |
| Ask the Engineer to inspect one issue. | The explanation identifies a clear next action. |
Record the actual result beside each test. After one approved change, repeat the affected test and one other important function.
Expected result: you can explain what passed, what remains uncertain and whether the service suits the project before trial expiry.
How can I evaluate the trial with a repeatable test?
- Test a public page, an administrator login, a form submission and the application-specific action that matters most, such as a test order.
- Record the expected result and the actual result. Keep screenshots free of customer data and credentials.
- After one AI-assisted change, repeat the original test and check that another important function still works.
Choose a test environment that cannot accidentally charge a customer or send a real fulfilment instruction. For a copied store, review payment, email and automation settings before testing. This makes the trial evidence useful when deciding both product suitability and the next hosting package.