Resources

What Should a Website and App Development Package Include?

Short answer

A website and app development package should define what each part does, which records they share, what you will pay, and who keeps both working after launch. Start with one customer journey instead of two feature lists. Rehost’s monthly bundle includes the website, customer app, and loyalty program together, with the agreed software work handled by one team.

This guide is for a business buying a public website and a customer app. It helps you compare the work and the ongoing service, whether you commission a project or choose a monthly bundle.

Check what the provider means by website and app

A website can help people find your business, read about services, and take a useful next step. It can also include booking, ordering, or account tools. A site that works on a phone is not automatically a separate mobile app.

A web app is software used through the web, often in a browser. Some web apps can also be installed on a device. MDN’s guide to progressive web apps explains this approach. The names can overlap, so ask the provider to show what customers will open and use.

Confirm whether the quote covers a public website, a browser-based customer tool, an iPhone and Android app, or a combination. Do not assume a quote for a web app includes both a marketing website and store-distributed mobile apps.

Give each part a clear job

Use the website for the tasks people need before they know your business well. Give the app a reason for regular customers to return. Keep the information that matters consistent across both.

Scope for a website and customer app
PartPossible customer jobWhat to agree
Public websiteFind services, locations, hours, offers, and a way to contact or buy.The pages, content, customer actions, and people who approve changes.
Customer appReturn to an account, booking, order, or reward balance.The first useful tasks, supported devices, access, and release work.
Shared recordsSee the right account details, activity, and offer rules in each place.The final record, supported connections, update timing, and corrections.

These are possible jobs, not a promise that every package supports every feature. Choose the few tasks your customers need first.

Test the handoff from website to app

Example only: a shopper finds a store’s website, checks the hours, and joins its loyalty program. Later, the shopper opens the customer app and sees the same account and reward balance. Staff update the program rules through the agreed process.

Ask the provider to show that whole journey. Does joining on the website create the right record for the app? What happens when someone uses a different email address or changes their phone number?

Decide where hours, offers, prices, and customer records are managed. A connection may keep some information in step. Other changes may need staff or the provider to update both places. Name that work instead of assuming it happens automatically.

Confirm your existing checkout, booking, payment, and customer tools. Connections depend on vendor support, permissions, account access, and the work in the agreement. Keep a clear fallback for a delayed or failed update.

Write one shared brief before asking for quotes

A short brief helps two providers quote the same job. List what you have, what must stay, and what customers should be able to do at launch.

  • Pages and content: the website pages, locations, languages, images, and copy needed.
  • Customer tasks: the first website and app actions, including what people can do without an account or download.
  • Records and connections: which tools hold the final sales, bookings, accounts, and reward balances.
  • Responsibilities: who supplies content, approves the work, answers customers, and handles updates.
  • Launch needs: the accounts, data transfer, testing, store review, and existing website move, where needed.

Separate the first version from later ideas. Ask what happens to the price and target date when the brief changes.

Compare the full bill and the work left with your team

A project quote may cover design and development while leaving hosting, updates, and support to a separate agreement. A monthly service may include ongoing work but still have usage limits and outside costs. Read what each includes.

Compare setup, design, content, development, connections, testing, and launch. Then include domains, hosting, developer accounts, software licenses, messages, and maintenance where they apply.

Ask who fixes a broken contact form, publishes new hours, handles an app release, and follows up when a connection stops working. Confirm response targets and included changes in writing.

Compare the first year and a normal year after any introductory offer. Keep the scope and expected usage the same in each quote. There is no useful single price for website and app development until those details are clear.

Plan the move from your current website

If you already have a useful website, decide what can stay before planning a replacement. Keep a record of important pages, customer actions, domains, and accounts.

If page addresses change, ask for a map from the old pages to the right new pages and a way to send old links there. Google’s site-move guidance describes preparing that map, setting up redirects, and monitoring the change.

Include that work in the quote rather than treating it as a design detail. Check key old links and customer forms before retiring the old site. A new design alone does not establish a search-traffic improvement.

Accept a working journey before announcing launch

Agree on the checks before work starts. Use test records and the devices your customers use. For each failed check, name who fixes it and who approves the result.

  1. Find important pages and use the main action on a phone and a computer.
  2. Send a test inquiry or booking and confirm it reaches the right person or system.
  3. Join or sign in through the supported website and app paths.
  4. Check that shared activity appears once on the right account.
  5. Try an error, a cancellation, and the agreed fallback for a failed connection.
  6. Check keyboard access, readable content, and a clear path to customer help.

If app-store releases are included, allow for the accounts, review materials, and corrections needed. An agreed build target does not guarantee store approval on that date.

For the rewards-specific brief and launch checks, read the loyalty app development buyer’s guide.

Confirm ownership, access, and leaving terms

Ask who controls the domain, hosting, store accounts, customer records, and software licenses. Confirm what can be exported, in what form, and what help is available if another team takes over.

For Rehost, customers retain the content and data they submit. Rehost owns its software, code, and designs unless a signed agreement says otherwise. Accounts, licenses, exports, handoff, and service-end terms follow that agreement.

Do not assume one bill transfers ownership of every tool. Put the notice period, final costs, and access after service ends in plain language.

When does the Rehost bundle fit?

Rehost is worth comparing when you need the website, customer app, and loyalty program built and run together. All three are included in one monthly bundle. Your team sets the business rules and approves changes; Rehost handles the agreed software work.

The Business bundle page explains the offer. Review current monthly pricing and terms, including the regular price after any introductory offer. The proposal confirms connections, usage, outside fees, included changes, and responsibilities.

If a working website and a simple reward card cover your needs, you may not need a full package. Our small-business loyalty app buyer’s guide can help you compare lighter options.

FAQ

Do we have to build the website and app at the same time?

No. Start with the work your customers need now. If the app will come later, agree on how accounts, content, and records will connect before choosing the first system. A staged plan still needs a clear scope for each stage.

Can we keep our current website or business tools?

Possibly. Review what works and what needs help before replacing it. The provider should confirm which tools can stay, which connections are supported, and any work or fees needed to keep them together.

Will customers have to download the app?

Only for the tasks that require the chosen app experience. Agree on what the public website can handle without an install or login. Give customers a clear alternative for essential information and help.

Bring one customer journey to the conversation

Bring your current website, business tools, and one task customers should be able to complete across the website and app. Use that to compare the build, the ongoing work, and the handoff.

Explore the Rehost website, app, and loyalty bundle and review the monthly price and written terms.

Need help with the next step?

Tell us what is not working. We will help you figure out what to do next.