Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. Three ways to meet the same need
  2. Five questions to ask before choosing
  3. Example: booking a class
  4. How SiteMonk scopes and bills the work
  5. What to prepare for the first conversation
  6. Related

Use an existing tool, integrate it, or build custom software?

Compare a ready-made tool, an integration and custom software by fit, ownership, full cost and maintenance. Understand which work belongs in a website build and which needs its own scope.

Start with the job you need done. If an existing service meets the requirements, using it may save development and upkeep. If it does not, identify the missing workflow before paying for an integration or custom software.

SiteMonk builds websites and software, and also helps businesses assess these choices. We check existing tools before proposing a custom build. The useful outcome is a suitable way to operate the business, not the largest development project.

Three ways to meet the same need

Route What you buy Who maintains what What to check
Use an existing service An account with a vendor; a link or embed on your website where appropriate The vendor runs its product; you own your account and business settings; the website team maintains the agreed connection Required features, subscription and usage charges, branding, accessibility and export options
Integrate existing services Work connecting systems that already do parts of the job Vendors maintain their products; an identified team maintains the connecting code, permissions and error handling Supported interfaces, data ownership, failures, ongoing costs and who fixes the connection
Build custom software A defined first release for a workflow existing tools cannot reasonably cover Your appointed team maintains the application and its dependencies; someone on your side owns the business process Scope, acceptance criteria, hosting, security, support, handover and future changes

An embed is not the same as an integration that moves customer records or payments. A vendor can keep its service online while your account settings or connection still need attention. Changing vendors can also require data export and replacement work.

Five questions to ask before choosing

Question Why it affects the decision
What must the customer or staff member complete? Write the whole task, including confirmation and what happens when it fails. A demonstration screen alone is not a working process.
What data, permissions or transactions cross the boundary? A link to an external booking tool and an application managing bookings itself carry different implementation and operating work.
Which requirements can the existing tool actually meet? Check a trial or a documented feature against your own scenario. Identify a real limitation before proposing custom work.
Who will keep the result working? Assign the website, vendor account, connection and business operations to named owners. Include updates and failures in the plan.
What is the full cost, and what happens if you leave? Count setup, subscriptions, usage, support, migration and staff time. Check which data and files you can take with you.

Login, payments or a changing list are reasons to examine the scope, not automatic proof that you need custom software. A provider-hosted checkout may be an existing-tool integration; a changing team list may be ordinary website content. A portal with its own permissions and records needs a different assessment.

Example: booking a class

This is an illustrative decision, not a report of a completed client project.

A studio wants people to choose a class, pay where needed, and receive confirmation. First, list the requirements: capacity, cancellations, reminders, staff access and the payment process. Then test an existing booking service against them.

If the service covers the workflow, the website may only need a booking entry or an agreed embed. If staff must copy bookings into another system, assess whether an integration would remove that work. If a necessary approval or scheduling rule cannot be supported, write down the gap and scope only the custom work needed.

Before accepting a proposal, ask to see the expected result for a successful booking, a full class, a failed request and cancellation. Check how records are received and reconciled, not just whether a booking button opens.

How SiteMonk scopes and bills the work

Type of work Scope and billing
Standard website build The written proposal records pages, content and agreed functions. Setting up supported existing tools within that scope does not add a separate development charge; you pay vendors’ subscriptions and usage fees directly.
Separately quoted website features Additional website functionality has an agreed scope and build price. Any additional Care charge and operating responsibilities are agreed before work begins.
MVP or custom software project We start with requirements and a ballpark estimate, then a detailed plan and budget if the range fits. Development and subsequent work are billed for actual time at the published rate. MVP maintenance has no fixed monthly Care fee.
Independent product design or technical advisory These have their own deliverables and time-based billing. A clickable design prototype does not include a production application unless that implementation is separately agreed.

The contract and current service pages define the applicable minimum charges, communication time and payment terms. A software project can have a completed, accepted first release; later work is separately planned. Its billing does not automatically become a website Care subscription.

What to prepare for the first conversation

Bring the task, the systems you already use, the people who need access, the information that must move and what an acceptable result looks like. Include tools you have tried and the specific reason they did not fit. We can then compare options or define a scope worth estimating.

For one common website feature, see how to display Google reviews . It compares a widget, plugin, custom connection and managed website work.

SiteMonk service scope checked on October 27, 2026. The booking scenario is illustrative; the right route depends on the actual requirements and tools available.