Knowledge hub
Answers on reviews and audits, solutions, and next steps.
Most questions people ask before they pick an entry point. Every answer links back to the page it came from.
Start here
The questions most people have first.
If you're deciding between a homepage review, an audit, or a project, these four usually answer it.
- 01
What happens after I submit a request?
Within one business day you get a short reply that confirms what we heard and names the next step: a time to talk, a shorter intake, or a tool that answers…
Read the full answer - 02
How do you decide what to fix first?
Impact first, then the cost to ship. A fix that unlocks pipeline this quarter beats a prettier long-term project. We name one first fix you can run this week,…
Read the full answer - 03
How is this different from a growth audit?
A growth audit pulls ads, CRM, and reporting into one story when teams disagree on what counts as an inquiry. A website review stays on the site and the…
Read the full answer - 04
Is implementation included?
No. The audit stands on its own. You keep the brief and ranked findings. Hand them to your team, to another vendor, or ask us to quote Solutions work. In that…
Read the full answer
Topic
Reviews & diagnostics
Not sure what is broken? These reviews find it and rank the fixes.
What is actually included in the website review?
Three things: a video walkthrough of the pages that matter, a PDF with fixes ranked by severity, and one named first fix. If we spot a bigger issue outside the site, we flag that too. Enough for a developer or vendor to quote from.
How long does it take?
We reply within one business day with scope. Most reviews come back within 5 to 7 business days of when we start, depending on how many pages are in scope.
How is this different from a growth audit?
A growth audit pulls ads, CRM, and reporting into one story when teams disagree on what counts as an inquiry. A website review stays on the site and the contact path: message, trust, calls to action, and the steps people take to reach you.
Does the review include implementation?
No. The review stands on its own. You keep the notes and can ship in-house, hand them to a vendor, or bring us in for implementation under Solutions if you decide a rebuild is warranted.
What happens after I receive the findings?
Most teams pick one or two high-severity items and ship them that week. Some use the ranked list to scope a larger redesign. If you hire us afterward, we start from the same list, not a new round of research.
Can you review an existing site, or only homepages?
Existing sites are the default. We look across the homepage, important inner pages, the contact path, and mobile friction. For homepage-only questions, the free homepage review is the right scope.
Can the review surface CRM, follow-up, or reporting issues too?
It can flag them. If the symptoms point to follow-up speed, intake routing, or reporting disagreement, we say so in the notes and point you to the right next step, not a bigger site scope.
What is included in the growth audit?
One written brief that traces an inquiry from first click to booked call across your whole path: ads, pages, CRM, and follow-up. Findings ranked by severity, one named first fix, and a straight call on where the real issue is. Then about 60 minutes live with your team.
How do you decide what to fix first?
Impact first, then the cost to ship. A fix that unlocks pipeline this quarter beats a prettier long-term project. We name one first fix you can run this week, not a generic top ten.
How is this different from the free homepage review?
The free homepage review stays on the first screen of one page. A growth audit looks at the whole inquiry path when the systems disagree: ads, pages, CRM, and reporting.
What access do you need from us?
Ad account read-only, CRM read-only, any dashboards your team argues about, and the landing pages that carry paid or organic traffic. We send a one-page access checklist after scope is set. No write access, no credentials pasted in email.
Is implementation included?
No. The audit stands on its own. You keep the brief and ranked findings. Hand them to your team, to another vendor, or ask us to quote Solutions work. In that case we build from the same list, not a new round of research.
Can this surface CRM, paid, reporting, and follow-up issues?
Yes, that is exactly what it is for. Most of the time the real issue is a handoff, a definition, or a reporting gap, not creative. We name which area is the issue and which areas are noise.
What happens after the findings?
You leave with a ranked list, one named first fix, and a clear call on where to spend next. Most teams ship the top items in-house or with their existing developer. If the audit shows the issue is narrower, say the site only, we hand you to the right next step.
How long does it take end to end?
Reply within one business day with scope and an access checklist. We start one to two weeks out. Written brief back in 7 to 10 business days after access lands. Live walkthrough scheduled the week after.
What exactly is included?
A map of your inquiry path from capture to booked meeting, a ranked list of where it breaks, and one named first fix to run this week. We also tell you what we ruled out. Returned inside a week.
How is this different from a website review?
A website review looks at the page before the form: what it says and whether it earns the click. The inquiry and follow-up review starts after the form submits: who gets the inquiry, how fast they reply, and what happens next. Different halves of the same path.
How is this different from CRM or automation work?
CRM and automation work is implementation: rules, fields, integrations, sequences. This review names whether those things are the real issue before you build. A lot of teams find the fix is a process or ownership change, not another tool.
What access do you need?
Read-only access to your CRM and, where relevant, your scheduler, form tool, and whatever inbox routing you use. A short written walkthrough of how an inquiry is supposed to move through the team. No production changes from us.
Is implementation included?
No. The review stands on its own. Your team, your existing vendors, or Busic Digital under Solutions can run the fixes. We quote build work separately and only when you ask.
Can it surface response time, routing, or ownership issues?
Yes, those are the most common findings. The review looks at when the first human reply actually lands, who owns the inquiry when the usual rep is out, and whether stages match how the team really works.
What happens after the findings?
You decide. Most teams fix the named first item within a week, then work down the ranked list. If the review points at the site or reporting instead, we route you there, no second discovery needed.
Topic
Advisory
When you want a ranked plan before anyone builds anything.
What is included in the operations and automation review?
A review of the workflows, handoffs, and repeat work in scope. A ranked plan that separates what should stay human, what can be automated safely, and what needs ownership cleaned up before anyone wires anything. You get the written plan, about an hour live with the team, and a clear first step.
Does this include implementation, or is it just the plan?
Just the plan. The review stops at the ranked recommendations and sequencing. Implementation happens afterward, so you can run it internally, hand it to another vendor, or bring it to Solutions. We only talk build work if you ask.
How is this different from Solutions work on CRM and automation?
Solutions is where we wire the integrations, workflows, and reporting. The review is the step before: deciding what should be automated, in what order, and what should stay manual or get cleaned up first. The review produces the plan; Solutions builds from it.
What access or context do you need?
A short written description of the workflows in scope, who owns which step today, the systems involved, and a few examples of where work stalls or repeats. Read-only access to relevant tools when it helps. We send a one-page checklist after scope is set. No credentials over email.
How do you decide what should stay human?
Judgment, approvals, client relationships, and exception-handling stay manual. If a step needs context a rule cannot capture, or the cost of getting it wrong is high, we do not automate it. Automation handles the repeatable scaffolding around the judgment work.
Is AI always part of the recommendation?
No. AI gets recommended where it actually helps: drafting, summarizing, triaging, classifying, and always with us reviewing anything that leaves the building. If AI does not reduce risk or save meaningful time, we say so rather than add it for show.
What do I get at the end?
A written plan: workflows reviewed, steps classified (keep human / automate / AI-assist / fix ownership first), ranked next steps with sequencing, and one named first step so your team knows where to start this week. Forwardable to ops, finance, IT, or a vendor without a meeting to explain it.
What happens after the findings?
You decide. Most teams run the first few items internally. If the plan names a step that needs real implementation work (CRM routing, reporting, integrations, or a website fix), you can route into Solutions or the matching review page. No second round of research.
Can this route into CRM, reporting, or website work later?
Yes. The plan often names where the real issue is. If implementation is CRM and automation, that routes to Solutions. If it is reporting visibility, that is Reporting and attribution under Solutions. If the issue is the page or follow-up, we route you to the website review or the inquiry and follow-up review.
What if ownership or data is still too messy to automate?
We say so plainly. Automation encodes whatever process you already run, so if ownership drifts or definitions are unclear, software just locks in the confusion. The plan will put process cleanup first and name what has to be true before any automation is wired.
What is actually included in the AI integration audit?
A written document, usually 6 to 10 pages: three to five ranked AI opportunities specific to your operation, the tools we would use with monthly costs, estimated hours saved per week, and what to do first.
How long does the audit take?
We reply within one business day with scope and a kickoff time. From kickoff call to delivered document is typically 7 to 10 business days, depending on how complex your operation is.
How is this different from a generic "AI strategy" engagement?
Most AI strategy work is slideware: frameworks and future-of-work language. This audit is specific to your business: named tools, named workflows, estimated hours saved per week. If we cannot find three to five real opportunities, we tell you and refund the scope.
Do you build the integrations after the audit?
Optionally. The audit stands on its own, and you can implement in-house using the document. If you want us to wire the integrations in, that falls under our operations and automation work, scoped separately.
What AI tools do you recommend?
Whatever fits the workflow. That might be ChatGPT, Claude, an automation tool like n8n or Zapier, or the AI already inside the tools you pay for. We are not locked into one vendor and we do not get kickbacks.
We already pay for ChatGPT and Claude. Do we still need this?
Often yes. Most companies pay for an AI tool and use 5% of what it can do. The audit looks at your specific operation and identifies where the tools you already have could absorb hours of manual work you have not connected yet. If the answer is 'you are already maximizing it,' we say so.
Topic
Websites
What to know before you fund a website project.
Is the free homepage review a sales call in disguise?
No. You get written notes you can use without us. If you want help with the fixes, we outline options when you ask. That is not a condition of the review.
Do I need a full redesign or smaller fixes?
We ship what moves the number first. Often copy, proof, and the primary call to action change outcomes without a from-scratch build. Full rebuilds are for when structure or tech debt is the real cap. We still sequence what ships first.
How does a homepage review turn into a build plan?
You receive a ranked list: what to fix, why, and in what order. A build quote maps those items to design, dev, and CRM work so budget tracks the list instead of a generic scope doc.
What CMS or stack do you require?
There is no default stack. We choose based on what your team can maintain, how fast it loads, and where leads need to land. The tool follows the outcome.
How long does website implementation take?
Small fixes typically ship in weeks. Larger builds follow a roadmap with timing set by approvals, assets, and how many layers we are fixing at once.
Is this a one-time project or ongoing?
Most work has a clear launch, then optional iteration when channels or offers change. Retainers are not the default. If you want ongoing help, we say so up front.
What if the real problem is ads or follow-up, not the site?
We tell you. A sharper site does not fix bad targeting or follow-up that nobody owns. We point you to the right solution page or to reviews and audits so you do not fund the wrong project.
Should we do a website review first, or just build?
Build right away if you already know your message and audience, and the page just does not show them yet. Start with a review when the team disagrees on who the site is for or what it should say. A short review is cheaper than a rebuild aimed at the wrong target.
Topic
Paid acquisition
Channels, budget, timing, and how ads tie to the site and follow-up.
Do you advertise on every platform?
No. We pick channels where your buyers actually look and your team can respond. The plan says where and why.
Our site is weak. Should we still run ads?
Usually not at scale. We tell you when the page is the issue. Often we send you to a homepage review or site work first so spend is not wasted.
How do you define success?
First we agree on what ads should produce for you. That might be sales, signups, donations, or booked calls. Then we measure cost against that number. Clicks alone are not success.
How long until we see a change?
Most accounts need a few weeks for learning and fixes. Big jumps depend on season, offer, and how fast creative and pages can ship. We set timing in the first plan.
How much budget do we need?
We size tests so one bad week cannot wipe your quarter. For a real range, request a project call. The number depends on your goals and your market.
What if follow-up is broken?
We say so. Better ads do not fix slow response. We send you to CRM and automation work when that is the issue.
Should we do a growth audit first, or just run ads?
Run ads if the offer converts, follow-up is tight, and you already know which channel you want to pressure-test. Start with an audit when spend has plateaued without a clear reason, or when leadership disagrees on what "working" looks like. The audit names the issue so we do not spend our way around it.
How involved do we need to be each week?
About an hour for most projects: approvals on creative and offers, a short check-in on pacing, and answers when buyer context matters. More in weeks where we ship new landing pages or change the offer, less once the account is steady.
What do you hand us when the project ends?
Account access stays with you, not us. You get the live campaigns, the ad copy library, and the tracking setup, all clearly labeled. Plus a short written plan for whoever runs it next.
Topic
CRM & automation
Ownership, routing, follow-up, and where automation helps vs. hurts.
Do we have to switch CRMs?
Usually no. We work with what you already run. We only recommend switching when your current system truly cannot do the job. If we do, we spell out the risk, the timeline, and who maintains it after launch.
We need more demand, not deeper CRM work. Now what?
We say that plainly. Cleaner records and better routing do not create pipeline or fix a weak offer. When demand, positioning, or the homepage is the cap, we point you to websites, conversion work, or paid acquisition, and keep CRM scope off the critical path until the volume is there.
What kinds of CRM and automation work do you actually build?
Routing and assignment rules, stages and required fields that match real work, integrations so forms, billing, or internal tools write to one record, and task rules that replace status meetings. Customer-facing sequences only where your team can reliably follow through. The goal is fewer manual hops, not more software.
Will automations overwhelm our team or spam contacts?
We design for limits: who owns the record, when a sequence pauses, and how often nudges fire. Internal automations should cut repeat questions and status chasing. External messages should match what your team can honor on the next real step, never a blast because the tool allows it.
What happens in the first few weeks?
Alignment and baseline first: who owns new work, shared definitions, duplicate cleanup, and routing that matches how you operate. We stand up a thin scorecard you can review weekly. Heavier workflows and cross-system automation land after ownership and data behave, not on day one.
How do we know it is working?
A short list tied to how you operate: response time, honest stage movement, and the outcomes your team already cares about. If the conversation drifts to vanity metrics, we steer it back.
Our data is messy. Should we automate anyway?
Automation amplifies whatever you feed it. We usually fix duplicates, required fields, and stage rules first, then automate. If the mess is really a disagreement about process, we pause and route you to advisory until leadership aligns on ownership and definitions.
People still work outside the CRM. Should we buy more software?
No. New licenses rarely fix adoption. We tighten accountability, lightweight habits, and clear “system of record” rules first, sometimes with reviews and audits, before we expand the stack. Software spreads unclear ownership faster, not slower.
Should we run a follow-up review before automating?
Usually yes if ownership is fuzzy, response time is slow, or leadership cannot point to one system of record. The review is cheap and keeps us from automating the wrong handoff. Skip it when ownership is already clear and you just need the build.
Topic
Reporting & attribution
Definitions, dashboards, and what to fix before the chart is the problem.
Can you get perfect multi-touch attribution?
No. Nobody can, and chasing it blocks decisions. We build views your team can defend in a real meeting: which channels drove which outcomes, at what cost. Useful beats theoretically perfect.
Which tools do you require?
We do not lock you into a vendor list. We build inside the analytics, CRM, and ad platforms you already run. If another tool would clearly cut manual work, we recommend it with plain scope and tradeoffs. You choose.
Sales and marketing disagree on the numbers. Where do you start?
Start with definitions, not software. We get one scoreboard in writing, then wire tags and CRM fields so the report matches it.
How long until we trust the weekly report?
Tags, events, and required fields often move within days once someone can approve changes. Deeper CRM cleanup or offline reconciliation may need a few weeks. You get concrete dates in the first plan, not open-ended timelines.
What if follow-up is slow, not the dashboard?
We tell you. A sharper chart does not answer the phone. We send you to CRM and automation work when response time is the issue.
Do we have to rebuild the site to fix attribution?
Not usually. Often forms, UTMs, and thank-you pages need fixes first. If the page is the part to fix first, we send you to Website design or Conversion improvements work and say why.
Topic
Conversion
Landing pages, forms, offer copy, and where testing actually earns its keep.
We need more traffic, not a prettier page.
If volume is the real gap, we say so and send you to Campaigns or whatever fills your pipeline. A sharper page does not fill an empty pipeline.
What do you count as success?
Whatever you already track: qualified leads, booked calls, or completed requests. Click rate alone is not the goal.
How fast do we see movement?
Copy and layout fixes can ship in weeks when you approve fast. Tests need enough weekly volume to read a winner. We set timing in the first plan.
What if follow-up is slow, not the landing page?
We tell you straight. A clearer form does not fix a cold inbox. We send you to CRM and automation work when response time is the limit.
Do we have to rebuild the whole site?
Not usually. Often one landing page and one form move the number first. Full rebuilds are for when the platform or structure needs the rebuild. We still ship what the ranked list says first.
Which pages should we prioritize first?
The ones closest to the money. Usually the homepage, the top-entry landing page from paid or referrals, and the form or booking step. We rank pages by visits times drop-off, not by what looks worst. Pretty rewrites on low-traffic pages do not move the number.
Do you ship changes, or just recommend them?
Both are possible. Default is ship: we write the copy, update the layout, and push it live with your approval. If your team prefers to implement, we hand over specs clear enough to build from without a back-and-forth. The change is the same; who clicks publish is your call.
How do you know a change actually worked?
We compare the conversion and inquiry-quality numbers before and after the change over a window long enough to read. When volume is high enough, we run an A/B test. When it is not, we use before/after with context on season and campaigns so we do not credit a change that just rode traffic.
Topic
Contact & next steps
What happens after you submit, how to decide where to start, and how to reach us.
What happens after I submit a request?
Within one business day you get a short reply that confirms what we heard and names the next step: a time to talk, a shorter intake, or a tool that answers your question faster. No long nurture sequences, no auto-booked calls. If we are not a fit, we say so and point you to who to try instead.
Still not finding the answer?
Start with a review, or send a note with your situation.
Most questions about fit, timing, or scope answer themselves once we can see the page, the lead path, or the report you're arguing about. Pick the path that matches where you are.
Fastest, async
Free homepage review
Written notes on message, proof, and the first action.
Get a free homepage reviewWhen follow-up is the mess
Lead flow checkup
A quick review on intake, routing, and response time.
Open lead flow checkupYou want a conversation
Request a project call
Bring your URL, the issue you have already named, and what a good lead looks like.
Tell us where you're stuck