The website-or-app question almost always arrives with a budget stapled to it. Three or four thousand dollars, a month of evenings, and a founder trying to work out which of the two it should go into. For most people asking, it's the website, it's one page, and it should take an afternoon rather than a month. The month goes somewhere else entirely, into the part nobody frames as a build decision: getting a human being to arrive on that page, and having something useful happen to them when they do.

The test: does anything have to be remembered?

Ask ten small business owners what they need and nine say "a website." What they usually mean is that they want to be found, booked and paid. Three separate jobs, and only the first one is a page. A website builder makes pages: pick a template, write up your services, publish. Every business should have one, because a business with no website looks like a business that closed three years ago. An app builder makes something that remembers. There's a database underneath, people have logins, records get created and pulled up again eight months later, and money moves in a way the system can track.

So write down what happens in the ninety seconds after a customer finds you. If it's "they read a bit, they spot the number, they ring," a website covers it. Go build one and spend the rest of the afternoon on something else. If the answer involves a slot, a deposit, an account, a history or a second visit, you've crossed into app territory. Say a dog groomer has forty regulars. What she runs is closer to a small database than a page: which dog, which coat schedule, who's overdue, who no-showed in March and still owes for it. A pilates studio selling ten-class packs has to know how many classes are left on each one. A mobile mechanic taking a deposit to hold Saturday morning has to know it was taken, by whom, for which Saturday. Pages don't hold that. Publishing is the job they were built for, and the limit shows up the first time you need to look something up.

Most of the time the "app" turns out to be a form with a login on it. A customer submits something, a dashboard shows a number back, and there's an account page and a password reset somewhere. That's a website with a database behind it, and calling it an app is what turns a two-week job into a six-figure engineering program on somebody's proposal. The other kind, the sort that earns a spot on a home screen, is a product decision. People keep an icon because they open it several times a week. If your customer needs you twice a year, they won't install anything.

The page has one job, and describing your company isn't it

The word "website" drags a lot of 2013 behind it: an About page, team headshots, a blog with two posts from launch week, and a contact form that lands in an inbox somebody checks on Tuesdays. That's a brochure. Brochures were never good at selling. They were good at being handed to a person already standing in front of you.

What you need is a landing spot. It's where the link in your outbound email goes. It's what somebody pulls up on their phone while they're on a call with you, and what the person who got your number from a neighbor types in at eleven at night to check you're a real business. The job is to take someone who is already slightly interested and turn that into something you can act on tomorrow morning. A short, plain, faintly ugly page does that fine, which is why the design budget is rarely the thing standing between you and a customer.

Why a page with add-ons gets expensive

The usual fix for a page that can't remember is to attach things. A booking widget here, a payment button there, an email tool, a contact form that empties into a spreadsheet. Each is its own account, its own login, its own monthly charge and its own private idea of what a customer is. The subscriptions are the small cost. The seams are the expensive part.

Your booking tool knows Maria took Tuesday at ten. Your payment tool knows someone paid forty dollars. Your inbox has her question about parking. Nothing joins those three facts, so you join them yourself, by hand, on a Sunday. Every add-on you hang off a page is a quiet promise that you'll personally be the integration.

When the thing has a database instead, you get a customer record, so a person exists once and their whole history sits under their name. You get logins, so customers can check their own bookings and stop emailing you to ask. You get an admin dashboard, so you can see today without opening five tabs. And you can take payments through your own Stripe account, so the money lands in your bank, your name is on the customer's statement, and the transaction history stays yours if you ever move platforms. Plenty of tools will take payments on your behalf and pass the money along on their own schedule. That works for some businesses, but owning the payment record feels abstract right up until the week it doesn't.

Nobody arrives at your page by accident

Search rankings for terms worth ranking for take a year of patient work and might not come. Paid traffic is a skill and a second budget on top of the first. What's left is going out and finding the people yourself, which is why website-versus-app is the wrong argument in the first place. The real decision is whether the month goes into building something or into demand for it, and only one of those has customers on the other side.

The usual advice is to buy the category leader for each slot: one tool to build, one for booking, one for outbound, one for contact data, one to answer the phone, and a connector holding the arrangement together. Another login and another monthly bill for each, and more importantly another boundary. Somebody fills in your form at 8:40 on a Tuesday night. Does the sequence that has been cold-emailing them know to stop? They call the next morning. Does whoever picks up know they filled in the form? A reply comes back saying "ask me in March." Which system moves them, and who is reading closely enough to notice? In every real founder's week the answer to all three is you, at exactly the hours you should be selling or asleep.

Here is what has to be true in the ten minutes after somebody lands:

  • The form writes into the same pipeline the outbound is running from, so a person who raises their hand stops getting cold emails and starts getting a conversation.
  • The number on the page is answered right then, at any hour, with a recording and transcript you can read later and a transfer to you mid-call when the call is worth taking.
  • Replies get sorted as they land, so a maybe-in-March doesn't vanish underneath fourteen bounces.
  • A quote can go out and be paid through Stripe without you leaving to do it somewhere else.
  • It's on your own domain, with your own pipeline stages and custom fields, because a company selling roof replacements doesn't sell the way one selling seats to a product team does.

None of that is website work. It's what happens after the page has done its bit, and it's the only reason the page was worth building.

What it costs, and what each plan includes

Rocketship is one product for getting customers: it finds buyers by name, emails them from your own Gmail, follows up, books the meeting, answers the phone so no lead is missed, and the site or app is where they buy. The Builder plan is $12 a month (monthly only) and is the site and app builder on its own. It does not include outreach, AI workers or phone answering. Getting customers starts on Launch at $24.99 a month ($20.83 billed yearly): one AI worker for email and AI phone calls, meeting booking, 50 leads a month and 30 voice minutes. It answers the number you already have through call forwarding, and a dedicated phone number isn't included (a line is $5 a month). Frontier is $79 a month and Mission Control is $149 a month, with more workers, leads and voice minutes.

When to build the app anyway

Sometimes the software is the product. A tool, a portal customers live inside, a calculator that is your actual differentiator rather than a lead magnet with a form bolted to it. Build that, and build it properly. Be honest about the step after, though. A published app sells about as well as a published page does, which is to say it sits there. The month you just spent is worth it only if strangers turn into conversations.

Build the page this afternoon, then judge it at the end of every week by how many strangers it turned into conversations. If that number stays at zero for a month, what went wrong wasn't your choice of website over app. Rocketship finds the buyers, emails them from your own Gmail, follows up, and books the meeting on its own. Plans that get you customers start at $24.99 a month (Launch), and every monthly plan starts with a 7-day free trial, card required. Answering your existing number is included; a dedicated line is $5 a month.