Start With a Small Paid Project Before a Big Contract
By CodexierPublished 4 min read
Choosing a supplier for a website, webshop, app or system is a big bet made on little evidence: a few meetings, a portfolio and a quote. The best way to reduce that risk is to buy something small first. A paid audit, a prototype or a single landing page lets you see how the supplier communicates, how they handle feedback and what their work looks like up close, before you sign for the large project. This guide explains how to pick that first project and what to watch while it runs.
Why a first small project reduces risk
Meetings and sales material show a supplier at their best. A real project, even a small one, shows ordinary working days: how quickly they answer, whether they ask good questions, what happens when something is unclear and whether the deadline holds. It also shows you how you work together, which matters as much as their skill. And it gives both sides a better basis for pricing the large project, because the scope is clearer after the first step.
Good first projects
A good first project is small enough to finish in a few weeks, clearly scoped, priced fixed, and useful on its own. These are typical examples from our own catalogue; the same types exist with most serious suppliers.
- Website or app health auditA review of an existing site or app: security, speed, updates and risks, with a prioritised list you can use with anyone.
- UX auditA review of where visitors get stuck and what to change, useful before any redesign.
- Landing pageOne page for one offer, which shows design, copy and build quality on a small scale.
- MVP planning blueprintScope, architecture and plan for a software product, before the build is priced.
What to evaluate during it
| Area | Good sign | Warning sign |
|---|---|---|
| Start-up | Clear questions, a written plan with dates | Work starts without clarifying goals |
| Communication | Answers within the agreed time, proactive updates | You have to chase for status |
| Feedback | Listens, explains trade-offs, adjusts | Defends everything or changes everything without thought |
| Deadlines | Delivered on time, or delays flagged early | Silent delays |
| Quality | Result works, is documented and matches the brief | Looks good but breaks on closer inspection |
| Honesty | Tells you what you do not need | Upsells at every step |
Write down your impressions as you go, not only at the end. Small irritations in a three-week project tend to be large ones in a six-month one. The questions in our guide on what to ask a web agency work well as a checklist.
Owning what you paid for
- Audit reports and plans are delivered as documents you keep and can share with other suppliers.
- Design files and prototypes are handed over in their original format, not only as images.
- Code for a landing page or feature lives in your repository or your website account.
- Accounts, domains and tools created during the project are registered to your company.
- The contract states that rights transfer to you on payment; see who owns your website.
Moving on or scaling up
After the first project, decide deliberately. If the work was good and the collaboration easy, ask for a quote on the next stage using what you learned. If it was not, you have a useful deliverable and have avoided a much larger mistake. Either way, ask the supplier for a short retrospective: what went well, what they would do differently, and what the next step would cost.
Decision rule: if a supplier refuses any small paid starting point and insists on the full contract immediately, treat that as information. When a trial is not worth it: for a simple, low-cost website from a supplier with verifiable references, the trial can cost almost as much as the project. We are happy to start small; our fixed prices are on the pricing page, and you can book a short call to pick a sensible first step.
Frequently asked questions
Should a trial project be free?
No. Free work gets lower priority and gives you no rights to the result. A small paid project is a real project, with a contract, a deadline and a deliverable you own.
Will a supplier accept a small project when I plan a large one?
Serious suppliers usually welcome it, because it reduces their risk too. Many already offer audits, discovery phases or prototypes as a first step.
Can the first project's cost count towards the large one?
Sometimes, if agreed in advance. More important is that the first project's output, such as an audit or a blueprint, genuinely reduces the scope or risk of the next.
What if we want a different supplier for the main project?
That is the point of the trial. If you own the deliverables, you can hand the audit, design or plan to another supplier and build on it.
Want to test us on something small first?
In a free 15-minute call we look at your larger plan and suggest a first project that is useful on its own, with a fixed price and a clear deliverable you keep.
Book a free 15-minute call