The 7 Backend Features Every Serious Small Business Site Needs

Visitors see your homepage. You run your business off the dashboard nobody else sees. The visible part of your site is maybe 10% of the value the site delivers. The other 90% is the backend infrastructure that quietly compounds over time. Here are seven things every serious small business site should have running in the background.

1. A real lead capture pipeline

"Contact form goes to email" is the bare minimum. The next level: form submissions get logged to a database, tagged with source/UTM, and trigger a notification with the lead's full context. Six months later, when the lead converts, you can trace which channel actually brought them in. Without this, you're flying blind on marketing ROI.

2. A self-serve admin dashboard

If updating a price or publishing a new blog post requires emailing your developer, you don't have a website — you have an expensive dependency. A real admin dashboard lets the owner edit content, see metrics, manage customers, and run the day-to-day without any technical handholding.

3. Custom analytics

Google Analytics is fine for traffic counts. It's terrible for understanding your funnel. Every site we build includes a small custom analytics layer that captures the events that actually matter: which CTA was clicked, how far down the page visitors scrolled, where in the form they bailed, whether they engaged with the AI chat. These are the numbers that drive real optimization.

4. Email infrastructure that doesn't break

SMTP from your dev environment "works" until your transactional email starts landing in spam. Real email setup means SPF, DKIM, and DMARC records configured properly, a reputable sending service (Postmark, Resend, SES, or even Gmail SMTP for low volume), and monitoring that catches deliverability issues before customers do.

5. Payment workflows that handle reality

Anyone can wire up Stripe Checkout. The subtle stuff is where projects fail: handling failed payments gracefully, sending receipts that don't look like spam, supporting refunds without manual database surgery, syncing with your accounting workflow. The first few payment edge cases set the tone for whether your customers trust you.

6. Automated alerts when things break

Sites go down. Forms stop submitting. APIs return errors. The question is whether you find out from your customers or from a push notification five minutes after it happens. We use ntfy.sh for monitoring everything we run — server health, error rates, payment failures. Costs nothing, runs forever, beats finding out from an angry customer.

7. Backup and recovery you've actually tested

Most sites have backups. Almost none have tested whether the backups actually restore. The first time you'll find out is the day you need them. Build the backup pipeline first, then run a drill: delete your database, restore from backup, verify everything works. Do it once before launch and you'll sleep better forever.

The compound effect

Each of these features by itself is nice-to-have. Stack all seven and your site stops being a website and becomes infrastructure. You can market without flying blind. You can run the business without touching code. You can sleep through the night knowing alerts will wake you only when they should.

The price difference between "marketing site" and "site with all seven of these" isn't trivial — usually a $3-5K starter site versus a $10-15K full-stack build. But the ROI is paid back in the first six months of operation, every time, because all seven of these features are revenue protectors and revenue accelerators.