Use an existing tool, or build it into your website?
Five questions that tell you when a feature belongs in a normal website, when a ready-made service is the smart answer, and when custom development is genuinely worth paying for.
Almost every small business website conversation reaches the same moment. You describe what you want — “customers should be able to book a slot”, “I want my Google reviews on the home page”, “people should be able to pay a deposit” — and someone has to say whether that is part of the website or a separate project.
Most studios answer with a feeling (“that’s not standard”). We answer with five questions you can apply yourself, and one rule that comes before all of them.
The rule that comes first: try the existing tool
Before anything gets built, ask: is there a mature service that does this already, which we can place inside your site so it looks like part of it?
Take a yoga studio owner who wants online class booking.
- Building it means writing a calendar, time slots, time zones, cancellation rules, reminder emails, and a sync with her phone calendar. That is a software project — and software projects need someone on call forever.
- Embedding Calendly or Acuity means she opens an account (roughly $15–$20 a month, paid to them, not to us), and we place it in her site and match the styling. That is part of a normal website build. No extra charge.
Nine times out of ten the second option is better for her: the tool has a whole company improving it, it gets fixed by them when it breaks, and she can switch to a different one whenever she likes.
The five questions
A feature is a separate project — what we call an add-on — if the answer to any of these is yes:
| # | Question | In plain terms | Why the line is here |
|---|---|---|---|
| 1 | Do visitors need an account or a login? | “Customers have their own password” | Logins mean password resets, hijacked accounts, permission mistakes, and legal responsibility for personal data |
| 2 | Does the website take money directly? | “Customers pay by card on the site” | Payment rules change every year, and when it breaks it’s real money — it can’t wait until next month |
| 3 | Is there a list of things that keeps changing? | “Products, orders, listings, a class schedule” | That data isn’t made once — it moves every week, and you will call the moment it’s wrong |
| 4 | Does it need heavy graphics or video? | “3D tours, interactive maps, editing video online” | More work than the rest of the site combined, and it slows the page down |
| 5 | Does it publish live tools or data to an AI platform? | “Claude can find and use what your business provides” | It needs a hosted service, secure permissions, platform review, and ongoing compatibility work |
These five are not arbitrary. They are exactly where the work stops being “a few more pages” and becomes databases, permissions, payment compliance, external platform review, and ongoing risk of things breaking after launch. Because the line follows real cost, the explanation always holds up.
Why “a website” and “a software project” are different purchases
Put simply:
- A website is finished when it launches. People visit it, read it, fill in a form to reach you. It doesn’t break because you stopped looking at it.
- A software project runs every day. It handles money, data, or logins. It needs someone watching it, and one day it will break.
A fixed-price website build covers the first kind. The second kind can absolutely be done — but it is a different purchase, and it changes how much effort it takes to look after your site every month. That is why an add-on has two prices: a one-time build cost, and a change to the monthly care fee.
How to use this section
Every guide here takes one common request and walks the same path:
- The problem in your words.
- What businesses used to do about it.
- What has changed (usually: a good tool now exists, or a platform opened up an official way to do it).
- Your options compared honestly — including the ones that don’t involve us — on cost, who maintains it, and what happens when the platform changes the rules.
- What we do, and who it is not right for.
Start with the most common request we get:
Google reviews on your own website
A widget, a plugin, custom code, or a managed site — compared.
Read
Related
- Pricing — what a build and monthly care include.
- Technical foundations — why our sites have no server, database or plugins to begin with.