Business Technology Audit: 15 Questions Before Your Next Website Project

Most website projects fail before design starts, not because the mockups were ugly, but because nobody asked how leads actually flow, whether forms work, or if hosting can survive a traffic spike. Owners spend thousands on redesigns that preserve every broken integration underneath.

A business technology audit answers the questions your next agency may not ask. It surfaces hidden risk, wasted spend, and the projects that actually move revenue. This article walks through 15 questions every service business owner should answer before signing off on a rebuild, re-platform, or major plugin investment.

Be honest with your answers. Gaps you find here are cheaper to fix than surprises six months into a project, and if you want structured help working through them, that is exactly what a business technology audit is for.

Question 1: Where do your leads actually come from?

Many owners say “Google” without data. Audit your last ninety days: organic search, paid ads, referrals, Google Business Profile, repeat customers. If analytics is broken or not installed, that is your first finding, you cannot optimise what you do not measure.

Red flag: Spending on ads while organic conversion pages have broken forms. Green flag: Channel-level lead counts you trust, reviewed monthly.

Related reading: local SEO for service businesses and signs your WordPress site is losing leads.

Question 2: Can you prove forms deliver every submission?

Submit a test enquiry from an external email address right now. Did customer confirmation arrive? Did the team inbox? Did CRM update? Silent form failure is epidemic, see broken WordPress forms.

Red flag: “We think forms work, we usually get emails.” Green flag: Monthly logged tests with timestamps and screenshots.

Question 3: What happens in the first hour after a lead arrives?

Map the path: notification → owner → quote → follow-up. Automation without ownership is worthless. Document median response time and who is accountable after hours.

Red flag: Leads sit in a shared inbox unassigned. Green flag: Documented SLA and automated acknowledgement within minutes.

Question 4: Does your site support how you sell?

If you sell structured hires, skip bins, man-and-van, trade slots, but the site only offers a contact form, technology is misaligned with revenue. Compare your intake to customer expectations in moving online quotes or skip bin booking online.

Red flag: Staff re-type website enquiries into job software. Green flag: Structured wizards feed operations directly.

Question 5: Who owns the website when something breaks?

Identify the person or partner responsible for uptime, form fixes, and plugin updates, not who built it in 2019. If ownership is “whoever is free,” emergencies become expensive.

Red flag: Original developer unreachable; nobody knows hosting login. Green flag: Named owner plus documented access in a password manager.

When hiring help, use criteria from how to choose a WordPress developer, technical skill matters less than revenue accountability.

Question 6: When did you last test on a real phone?

Desktop-perfect sites fail on mobile networks with autofill quirks and slow checkout. Test quote and contact flows on 4G, not office Wi-Fi.

Red flag: Mobile bounce rate high on conversion pages with no investigation. Green flag: Regular mobile tests documented; Core Web Vitals reviewed, see Core Web Vitals explained.

Question 7: Is your hosting aligned to revenue risk?

Shared hosting may suffice for brochure sites; booking-heavy WooCommerce stacks often need better resources, staging, and backups. Know where the site lives, plan limits, and support response times.

Site profile	Minimum hosting expectation
Brochure + contact form	Managed WordPress, daily backups
Quote wizards, moderate traffic	Staging, SSL, uptime monitoring
WooCommerce bookings + payments	Performance headroom, off-site backups, tested restore

Red flag: No backup restore tested in the last year. Green flag: Documented restore drill with recovery time noted.

Question 8: What data would you lose in an outage?

Orders, leads, customer history, booking calendars, quantify impact of four-hour downtime during peak season. That number should inform hosting and maintenance spend.

Red flag: Backups exist but nobody knows how to restore. Green flag: Recovery procedure written and tested.

Question 9: How many plugins touch checkout or forms?

Plugin overlap causes conflicts and silent failures. List every plugin involved in forms, email, CRM sync, payments, caching, and security. Mark which are essential versus experimental.

Red flag: Two form plugins, three SEO plugins, unknown custom code. Green flag: Minimal stack with documented purpose per plugin.

Context: WordPress for service businesses and why plugin updates break sites.

Question 10: Are updates tested before production?

Revenue sites should not auto-update everything blindly. Staging, backups before updates, and rollback plans are baseline, detailed in monthly maintenance plans.

Red flag: “We update when WordPress nags us.” Green flag: Scheduled maintenance windows with post-update form and checkout tests.

Question 11: Does security match your exposure?

Sites handling payments and personal data need strong passwords, 2FA on admin, limited user roles, firewall, and malware monitoring. Small sites are frequent targets, not because hackers care about your brand, but because WordPress is ubiquitous.

Red flag: Admin username “admin,” shared login, no 2FA. Green flag: Security checklist completed with ongoing monitoring.

Question 12: Can you export your data without a developer?

Vendor lock-in hurts when you change agencies or platforms. You should export orders, form entries, customer lists, and content without emergency contractor fees.

Red flag: Critical data trapped in proprietary plugins with no export. Green flag: Documented export paths and periodic CSV backups.

Question 13: What does success look like in numbers?

Define targets before a rebuild: lead volume, conversion rate, average response time, online booking percentage, cart abandonment. “Look modern” is not a metric.

Metric	Example baseline to track
Form conversion rate	Visits to key landing page → submissions
Median response time	Minutes from submit to human contact
Online booking share	% jobs booked without phone tag
Page speed (mobile)	LCP on quote and checkout URLs

Red flag: No analytics baseline before project kickoff. Green flag: KPIs agreed with agency and reviewed quarterly.

Question 14: Are integrations documented?

Map every connection: forms to CRM, Woo to accounting, chat to email, ads to landing pages. Note API keys location, renewal dates, and who pays for SaaS seats.

Red flag: “The old guy set up Zapier, not sure which zaps.” Green flag: Integration diagram or spreadsheet updated when tools change.

Question 15: Is the proposed project solving the real bottleneck?

The most expensive mistake is a beautiful redesign that ignores broken forms, slow checkout, or missing booking logic. Ask: “If we change nothing but fix the top three audit findings, do we hit our revenue goal?”

Often yes, which means a full rebuild can wait. Compare build options with WordPress vs custom booking systems before committing budget.

Red flag: Project scope is pages and colours only. Green flag: Scope ties to lead flow, bookings, and measurable KPIs.

Score your readiness

Count red flags honestly. This is not pass/fail, it prioritises spend.

Red flags	Interpretation	Suggested focus
0–3	Generally healthy; optimise and plan growth	Performance, SEO, selective features
4–7	Material risk; patch before big projects	Forms, follow-up, maintenance, security
8+	Critical; redesign alone will not help	Full audit, stabilise revenue paths first

Work through gaps systematically. Many align with ongoing care in website maintenance plans rather than one-off projects.

What a professional audit adds beyond this list

Self-assessment catches obvious gaps. An external audit adds form submission traces, server-level checks, plugin conflict review, and prioritisation weighted by revenue impact, not just a laundry list. You receive a sequenced plan: stabilise lead capture, then performance, then new features. That order prevents paying for redesign while forms still fail.

Bring analytics access, hosting credentials, and CRM exports to an audit session. The process works best when someone who handles daily enquiries joins the call, they know where technology fights operations even when dashboards look fine.

From audit findings to a twelve-month roadmap

Group findings into quick wins (form tests, SMTP fix, acknowledgement emails), medium projects (quote wizard, Woo checkout cleanup), and strategic bets (new booking product, CRM migration). Assign rough cost and impact to each. Most service businesses should clear quick wins in thirty days before funding medium projects, cash flow and morale improve when leads stop leaking immediately.

Revisit the fifteen questions quarterly. Technology drifts; plugins update; staff turnover loses passwords. A lightweight quarterly re-score prevents another crisis rebuild in three years.

Conclusion

These fifteen questions expose what pitch decks hide: whether your technology supports how you actually win work. Leads, forms, follow-up, hosting, security, integrations, and metrics, not homepage hero images, determine whether your next investment pays back.

Answer them in writing. Share answers with any agency or developer before signing scope. Fix red flags that cost money today before funding cosmetic change.

If you want an experienced second pair of eyes, someone who maps findings to a prioritised action plan rather than a sales deck, book a business technology audit. It is the fastest way to turn “we think the site is fine” into a clear list of what to fix, what to ignore, and what to build next.

Your website should be a reliable revenue system. These questions show whether it is, and where to start if it is not.

Block thirty minutes, answer all fifteen without guessing, and count your red flags. If you are at four or more, skip the redesign quote until stabilisation is scoped, or start with an audit so you are not guessing which four matter most.

The audit page walks through hosting, forms, bookings, security, and performance with you, not a generic PDF checklist. Bring your red-flag count and we prioritise what protects revenue first.

Whether you audit alone or with help, written answers beat vague assumptions. Future you, and any partner you hire, will thank you for the clarity.