Shoppers no longer start every product search on Google. A growing share now ask ChatGPT, Perplexity, Google AI Mode, or Gemini for recommendations before they ever see a search results page. For WooCommerce store owners, this shift is quiet but measurable: paid traffic stays steady, organic traffic slides, and brand searches tick up a few weeks later for reasons the dashboard cannot explain.

Generative engine optimization, often shortened to GEO, is the practice of making sure your store and your products get surfaced when buyers ask AI engines for recommendations. The playbook is different from traditional SEO, and WooCommerce stores have a specific set of technical and content levers to pull.

This guide covers the ranking signals that matter for product queries, the on-site changes that move the needle, the WooCommerce-specific setup that most stores miss, and the measurement approach that separates real progress from vanity metrics.

What GEO means for a WooCommerce store

GEO is not the same as writing content for ChatGPT. That is prompt engineering, which is useful for content production but does not move your visibility inside AI engines by itself. GEO is the discipline of structuring your store, your content, and your brand presence so that when a buyer asks an AI engine for product recommendations in your category, your products and your brand are what the engine recommends.

Three implications follow from that definition for every WooCommerce operator. The work spans on-site content, product data structure, and off-site brand signals, and most stores need help with at least one of those three areas before results start to compound. For brands starting fresh on this, specialized generative engine optimization services can map the current baseline and prioritize the first 90 days of work. The first implication is about citation.

Citation is the new category ranking. When an LLM recommends three products in response to a shopping question, those three brands have won the equivalent of top-three category rankings on Google. The brands not mentioned may as well not exist for that query.

Product content gets extracted, not browsed. AI engines read your product page and pull out the facts that match the buyer’s question. If your facts are buried in marketing prose, they get skipped. If they sit in clean structured blocks, they get cited.

Reviews and third-party signals matter more. AI engines weigh what independent sources say about your product almost as heavily as what you say about it yourself. A product with 50 real reviews on structured platforms outranks a product with slicker marketing copy almost every time. Monitoring, encouraging, and syndicating reviews at scale is where many stores partner with a professional SEO company that handles the technical setup and the ongoing reputation workflow in parallel.

How AI engines pick product sources

There is no public algorithm, and vendor documentation is thin. What follows comes from observed behavior across live stores. Treat these as working patterns, not confirmed rules.

Signal 1: Top-10 Google organic presence. AI engines, especially Gemini and Google AI Overviews, draw heavily from pages that already rank in Google’s top 10 for the query. If your product category pages are on page 2, GEO work is downstream of fixing your organic rankings first.

Signal 2: Structured product data. Schema markup, specifically Product schema with price, availability, review data, and specific attributes, correlates strongly with product citation rates. Pages with broken or missing schema get cited less often even when their content is similar.

Signal 3: Review freshness and depth. AI engines favor products with recent reviews from multiple sources. A product with 30 reviews from the last six months outperforms a product with 300 reviews that are all three years old.

Signal 4: Specific attribute coverage. Pages that answer specific sub-questions (“Is this waterproof?” “What is the heel-to-toe drop?” “Does it come in wide sizes?”) get cited for the long-tail queries where those attributes are mentioned. Vague product descriptions miss these queries entirely.

Signal 5: Brand consistency across the web. Product descriptions, brand positioning, and category framing should match across your site, your marketplaces, and the review platforms where your products appear. Inconsistency confuses the entity graph AI engines rely on.

Signal 6: Third-party editorial coverage. Being mentioned in Wirecutter, Reddit threads, YouTube reviews, and vertical publications feeds AI engines signals they trust more than brand-owned content.

Product page structure that gets cited

Most WooCommerce product pages are built for human browsers who scroll and skim. AI engines read differently. They extract clean, self-contained statements of fact and skip over prose that requires context to make sense.

A product page restructured for GEO looks like this:

Top of page: a direct answer paragraph. Three to five sentences that state what the product is, what it is for, who it fits, and what the key differentiator is. Written as plain facts, not marketing copy.

Specifications block. A clearly labeled section with every attribute a buyer might filter on: dimensions, weight, material, compatibility, warranty length, country of manufacture. Use a definition list or a two-column table, not a bulleted paragraph.

Use-case section. Short paragraphs or bullet points answering “this is right for you if” and “this is not right for you if.” AI engines cite these when buyers ask situational questions.

Comparison callout. One short block comparing the product to the two or three closest alternatives on specific attributes. This gets cited heavily for “X vs Y” prompts.

FAQ block with FAQPage schema. Six to twelve genuine buyer questions answered in two to four sentences each. These get extracted almost directly into AI answers when the questions match buyer prompts.

Review summary with structured markup. Not just the star rating, but a short paragraph summarizing what reviewers consistently praise and criticize. Mark it up with Review schema.

This structure can replace the typical “long description + specs tab” pattern on a WooCommerce product page. Both the native block editor and the common page builders (Elementor, Divi, Bricks) can lay this out without needing custom code.

Review patterns AI engines favor

Reviews are one of the three or four signals that move AI citation rates the most. Three patterns consistently outperform the rest.

Recent over voluminous. Twenty reviews from the last three months outweigh two hundred reviews from four years ago. Reach out to recent buyers with specific review requests at the 14-day post-delivery mark.

Detailed over star-rated. A written review that mentions specific use cases, specific pros, and specific cons gets referenced in AI answers. A five-star review with no text is close to invisible.

Multi-platform over single-platform. Reviews on your own site, Google, Trustpilot, Judge.me, Yotpo, and vertical review sites all feed into the AI engine’s picture of the product. A product with reviews only on your own site looks thinner than a product with the same volume spread across three platforms.

For WooCommerce stores specifically, syncing reviews to Google Shopping, to a review aggregator like Judge.me or Yotpo, and to the relevant vertical review platform is a one-time setup that pays off for the next 24 months.

WooCommerce technical setup for AI visibility

Beyond content changes, four technical items materially move AI citation rate for WooCommerce stores.

Product schema completeness. The default WooCommerce Product schema covers price and availability. Extended schema with aggregateRating, review, brand, GTIN, MPN, and specific product attributes gets your pages cited at measurably higher rates. Plugins like Rank Math and Yoast SEO Premium handle the common extensions, but complex catalogs often need custom schema templating.

Category and taxonomy structure. AI engines read your category structure to understand what each product is. Flat category structures (“Shop All”) get cited less than hierarchical structures (“Mens > Jackets > Waterproof > Three-Layer”). Rebuild your taxonomy if your category pages are not structured for extraction.

Image optimization for multimodal engines. Gemini and increasingly ChatGPT read product images as part of the answer. Original images with real alt text, descriptive file names, and ImageObject schema contribute to citation rates in ways that stock photos with “image-01.jpg” do not.

llms.txt file. A newer standard, similar to robots.txt, that tells AI engines which pages on your site are canonical. Adoption is patchy but growing. Costs nothing to publish and future-proofs your store.

Core Web Vitals for product pages. Fast, stable product pages get cited more often than slow ones on the same topic. For WooCommerce specifically, hosting quality and product-page bloat (page builders stacking too many widgets, too many related-product queries) are the two biggest Core Web Vitals killers.

Off-site signals that compound

On-page work has a ceiling. The ceiling is your brand’s presence across the sources AI engines treat as authoritative. Four off-site signals matter more than most WooCommerce operators realize.

Reddit and specialty forum presence. Reddit is one of the most-cited sources in LLM shopping answers. Participating in relevant subreddits as a known brand presence (not spamming) feeds signals that get your products mentioned in AI responses. The Reddit SEO angle is a GEO strategy by itself.

YouTube review coverage. Independent YouTube reviews of your products get cited in AI answers more than most store owners expect. Sending products to vertical YouTubers for honest review (not sponsorship) builds this signal over 6 to 12 months.

Vertical publication coverage. For every eCommerce category there are three to five trade or enthusiast publications whose reviews AI engines treat as high-signal. Getting your products reviewed in those publications pays off for years.

Consistent brand descriptions everywhere. Your product category framing on your own site, on Amazon, on Google Shopping, and in press releases should say roughly the same thing. Inconsistency weakens the entity signal AI engines use to identify your brand.

Measuring AI search visibility for product queries

You cannot improve what you cannot measure, and the measurement approach for product queries is slightly different from the content-piece approach.

Four metrics worth tracking weekly.

Prompt-set citation share. Build a list of 50 to 100 buyer prompts your ideal customer would type into an AI engine (“best waterproof hiking boots under $150,” “most comfortable office chair for tall users”). Check how often your brand or domain is cited across ChatGPT, Perplexity, Google AI Mode, and Gemini. Track the trend over months, not weeks.

Category share of voice. Of the brands cited in your category prompts, what percentage of citations are yours? This is the number that maps most directly to commercial outcome.

Attribute coverage. For long-tail prompts that mention specific attributes (“waterproof hiking boots that come in wide sizes”), are you being cited? Attribute gaps surface as product-page content gaps.

Downstream brand search lift. Six to twelve weeks after citation share improves, brand searches on Google tend to follow. This is the clearest lagging signal that AI visibility is working.

Tools like Peec AI, Otterly, Ahrefs Brand Radar, and Semrush AI Toolkit automate the tracking. Starting out, a 20-prompt weekly manual check in incognito mode is enough to see the trend.

Common mistakes WooCommerce stores make

• Treating GEO as a replacement for SEO instead of a layer on top of it (if your product pages do not rank, they will not get cited either)
• Rewriting product pages into thin, Q&A-only format that hurts conversion for human visitors
• Ignoring reviews because they are “the marketing team’s job” when they are actually the single biggest GEO signal for eCommerce
• Over-optimizing for ChatGPT and forgetting Perplexity, where B2B and research-heavy buyers often start
• Measuring GEO by referral traffic alone, when the real signal shows up in brand search weeks later
• Skipping schema completeness because the default WooCommerce output “looks fine”
• Treating off-site entity work as optional, when it is the ceiling on how far on-page work can take you

Closing thought

GEO for eCommerce is where SEO was fifteen years ago: measurable, winnable by the brands who invest early, and about to become table stakes. WooCommerce stores have an advantage because the platform is flexible enough to accommodate the schema, content, and taxonomy changes GEO rewards. The stores that act now compound a lead that gets harder to close as more category competitors catch on.

Start with your top-20 product pages. Rewrite them for extraction, complete the schema, sync reviews across platforms, and set up a weekly tracking cadence. The first results tend to show up in brand search lift within three months, and in citation share within six.

Here’s the thing about scaling an SEO agency. Everyone makes it sound easy. Sign more clients, hire a few people, watch the money roll in. If only.

The truth is, growing an SEO agency while still delivering results that actually move the needle for clients is one of the trickiest balancing acts out there. Ever noticed how some agencies start strong, then quietly fall apart once they hit a certain size? It happens more than you’d think.

So let’s talk about what actually works.

Why Scaling Breaks So Many Agencies

Picture this. An agency lands five new clients in a month. Great news, right? Except now the same team that was comfortably handling ten accounts is suddenly juggling fifteen. Quality slips. Reports get rushed. Client calls get shorter and vaguer. Three months later, two of those new clients walk.

This is pretty much the oldest story in the agency world.

The problem usually isn’t the sales side. Plenty of agencies are great at winning work. The problem is everything that happens after the handshake. Delivery, communication, and keeping existing clients happy while chasing new ones.

Scaling done well means building systems that hold up when the pressure comes. Not heroics. Systems.

Standardise the Boring Stuff First

Nobody got into SEO because they love process documents. But the agencies that scale without imploding are the ones that write things down.

Think about it. If every account manager runs audits their own way, uses different tools, and reports in whatever format they fancy, chaos is only a matter of time. When someone leaves, their knowledge walks out the door with them.

The fix is kind of dull but it works. Document your audit process. Standardise your reporting. Create templates for onboarding. Build a repeatable way of doing keyword research so a new hire can follow it without needing someone looking over their shoulder for a month.

This part’s a bit tricky because over-standardising can make work feel robotic. SEO still needs human judgement, especially with content and strategy. The trick is standardising the repetitive stuff so your team has more brainpower left for the creative, strategic parts that genuinely need it.

Hire Ahead of the Pain, Not After

Most agencies hire too late. They wait until the team is drowning, then scramble to find someone, then spend weeks training that person while everyone’s already stretched thin.

By then the damage is done.

Smart agencies hire just before they need to. Yes, it costs money upfront. Yes, it feels uncomfortable paying someone who isn’t fully booked yet. But a well-trained team member who’s ready when the new clients arrive is worth every cent of that early investment.

The alternative is burnout, and burnt-out teams produce burnt-out work. Clients can always tell.

Don’t Let Reporting Become Theatre

Let me say something slightly controversial. A lot of SEO reporting is pretty much performance art.

You know the ones. Twenty pages of charts that nobody reads, filled with metrics that sound impressive but don’t actually tie back to the client’s business goals. Impressions are up! Great. Did revenue move though?

ROI is the only language most clients actually care about. Rankings are nice. Traffic is nice. But if that traffic isn’t turning into leads, sales, or whatever the client defines as success, you’re decorating a cake nobody’s going to eat.

The agencies that keep clients long term are the ones that connect their work to money. Simple as that. They talk about conversions, cost per acquisition, and real outcomes. They’re honest when something isn’t working and quick to explain the plan to fix it.

Actually, that honesty thing matters more than people realise. Clients don’t expect perfection. They expect to be told the truth and shown a path forward.

Learning From the Ones Who Get It Right

If you want to see what good looks like, it’s worth studying agencies that have already cracked the scaling puzzle. Some of the top Australian SEO agencies have built reputations precisely because they nailed the balance between growth and genuine results, and there’s a lot to learn from how they operate.

Anyway, here’s the bit worth remembering.

Scaling an SEO agency isn’t about doing more things. It’s about doing the right things repeatedly, keeping your team sharp, and never letting growth come at the cost of the results that got you clients in the first place.

Get that balance right and the rest tends to follow.

For most of the last two decades, software companies and service businesses priced in a way that felt almost natural. You charged per user, per seat, per hour or per retainer, and revenue grew as your customer added more people or bought more of your time. That model worked because the value of the product was tied to how many humans were using it. When AI agents started doing the work itself, that link began to break, and founders who still price the old way are slowly discovering that their best feature is shrinking their own revenue.

Think about what happens when your product gets genuinely good at automating a task. A customer who once needed ten support seats might now need four, because the software resolves a large share of tickets on its own. The customer is getting more value than ever, and you are getting paid less for delivering it. That is the quiet problem sitting underneath a lot of AI-era businesses, and it is why pricing has become one of the most important strategic decisions a founder can make right now.

Why Per-Seat Pricing Is Losing Its Logic

Seat-based pricing assumes that more users means more value. In the cloud era that assumption held up well, because a shared system became more useful as more people inside a company logged in and collaborated. AI flips the equation. The value now comes from the work the software performs on the customer’s behalf, whether that is answering a support question, qualifying a lead, drafting a contract or reconciling an invoice. The number of humans logging in matters far less than the volume and quality of the work getting done.

The biggest players have already moved. Intercom prices its Fin AI agent at $0.99 per outcome, charged at most once per conversation, and it only bills when the customer’s issue is actually resolved or a configured workflow is completed. Zendesk publishes a price per automated resolution, with committed resolutions at $1.50 each and pay-as-you-go resolutions at $2.00 on its current pricing page. Salesforce started Agentforce at $2 per conversation and then introduced Flex Credits in May 2025, where a standard agent action costs about ten cents, and it lets customers shift spending between human user licenses and digital labor as their needs change.

None of these companies abandoned seats entirely. What they did was add a second unit of value that tracks the work itself, and when the largest software companies redesign how they charge, small agencies, consultants and one-person software businesses usually follow.

This conversation from a16z, with general partner Martin Casado and Metronome CEO Scott Woody, explains clearly why the value metric in software is shifting from users to output and what that means for how you charge.

The Three Pricing Models Founders Are Choosing Between

Once you accept that seats alone no longer capture value, you are left with three broad options. Each one has a place, and the right answer depends on how predictable your customer’s results are and how much risk you are willing to carry.

Usage-Based Pricing

Usage pricing charges for consumption, such as the number of actions an agent takes, documents it processes or minutes of voice it handles. It is easy to measure and scales naturally, which is why so many AI platforms start here. The weakness is that usage is not the same as value. A customer can burn through thousands of actions without getting a result they care about, and when the invoice arrives they start asking hard questions. It also creates bills customers cannot forecast, which slows renewals.

Outcome-Based Pricing

Outcome pricing charges only when a defined result is achieved, such as a resolved ticket, a qualified meeting booked or an invoice collected. It is the cleanest alignment between what the customer wants and what you get paid, and it makes the sales conversation remarkably simple because the buyer only pays for success. The catch is that you carry the risk. If your product underperforms, or if the customer’s own processes get in the way, you absorb the cost. Outcome pricing also requires an agreed definition of success, and that definition has to be measurable without endless arguments.

Hybrid Pricing

Hybrid pricing combines a base platform fee with a usage or outcome component on top. Fin shows how this works in practice, with its help center describing a $49 monthly base plan for teams using Fin with their existing helpdesk, which includes 50 outcomes before the per-outcome charge applies. For most founders this is the most practical starting point, because the base fee protects your cash flow and covers your fixed costs while the variable component lets your revenue grow alongside the value you deliver.

How to Choose the Right Unit of Value

The hardest part of moving away from seats is deciding what you will actually charge for. A good unit of value has three qualities. The customer must recognize it as something they want, you must be able to measure it automatically, and it must be something your product has meaningful control over. A resolved support ticket passes all three tests. Revenue growth for a client usually fails the third one, because too many outside factors affect it, and you will end up arguing about attribution instead of doing work.

Start by listing the results your customers already talk about when they describe why they bought from you, in renewal conversations, testimonials and cancellation reasons. For a bookkeeping service it might be a closed month delivered on time, and for a lead generation agency it might be a booked meeting with a buyer who matches the agreed profile.

Then test whether you can measure that result without manual work. If every invoice requires a debate about whether an outcome counted, the model will collapse under its own friction. The companies doing this well publish precise definitions. Intercom, for example, explains exactly when a conversation counts as resolved and states that it does not charge if a customer later returns to the same conversation needing more help. That level of clarity is what makes customers trust a variable bill.

Protect Your Margins Before You Promise Outcomes

Outcome pricing sounds attractive until you realize that your own costs are now variable too. Every task an AI agent completes consumes model calls, compute and sometimes third-party services, and if a difficult customer needs five attempts to reach one billable outcome, your margin on that customer can disappear.

Before you change your pricing, track the true cost of delivering a single outcome across a meaningful sample of real customers. Include model costs, any human review, support time and the attempts that fail. Then set your price with enough room to absorb the bad months. It also helps to understand the wider economics of AI, because the cost of the underlying models has been falling quickly, which can either widen your margin or invite competitors to undercut you depending on how you position the offer.

A few guardrails make this much safer in practice:

• Set a minimum commitment. A base fee or a minimum monthly volume protects you from customers who sign up, test lightly and leave you carrying the setup cost.
• Define what does not count. Spell out which situations fall outside the outcome, such as incomplete information from the customer or requests outside the agreed scope.
• Give customers spending controls. Usage alerts and hard caps reduce the fear of a surprise bill, which shortens sales cycles and reduces churn.
• Review pricing every quarter. Model costs, customer behavior and competitor offers are moving too fast for an annual pricing review to keep up.

What This Means for Service Businesses and Solo Founders

This shift is not limited to software companies. Agencies, consultants and freelancers face the same pressure, often more sharply. If you bill by the hour and AI tools cut your delivery time in half, your income drops unless you change how you charge.

The answer for service businesses is to package results rather than time. A fixed price for a defined deliverable, a retainer tied to agreed monthly outcomes or a performance component on top of a smaller base fee all let you keep the productivity gains that AI creates instead of handing them straight back to the client.

For founders who want to bootstrap a startup or a lean services company, higher margins on each engagement mean growth can be funded from revenue, and pricing on outcomes also changes the type of customer you attract. Buyers who care about results tend to be more decisive and less price sensitive than buyers who compare hourly rates.

How to Make the Transition Without Losing Customers

Changing your pricing model is unsettling for existing customers, so the transition needs care. Start with new customers rather than forcing the change on your entire base at once. Run the new model alongside the old one for a period, and show existing customers what they would have paid under each structure. When the outcome model is fair, many will choose it on their own, and the ones who do not can stay on legacy pricing until a natural renewal point.

Be transparent about why you are making the change. Customers respond well when you explain that you want to be paid for results rather than access, and badly when a pricing change looks like a disguised price increase. If the new structure costs some customers more, make sure they can see the additional value and offer a transition period.

Finally, build the measurement before you change the invoice. Nothing damages trust faster than a customer finding a mistake in a bill that is supposed to reflect the value they received.

Pricing Is Now a Strategic Advantage

Many founders treat pricing as something to set once and revisit only when revenue stalls. That will not hold up in a market where AI keeps changing what a product can do and what it costs to deliver. The founders who win the next few years will be the ones who treat pricing as a core part of strategy, who understand their cost per result and who are willing to tie their revenue to the value they create.

The good news is that this is one of the few major business decisions you can test without enormous risk. Pick one product or one service, define a clear outcome, measure your true cost of delivering it and offer it to a handful of new customers. You will learn more from those conversations than from months of spreadsheet modeling, and you will be building a business whose revenue grows as your product gets better instead of shrinking because of it.

A guy I know runs a 14 person warehouse supply shop outside Columbus. He paid his crew for 38,400 hours last year. When he finally sat down with actual clock data instead of gut feel, the number he could defend was closer to 34,000. That’s a whole employee he was paying for who never showed up. Not theft, not fraud. Just a decade of rounding, of “close enough,” of a supervisor who liked his team too much to say anything.

Most owners I talk to assume their payroll is roughly accurate. It isn’t, and the gap rarely comes from the person you suspect. It lives in the spaces nobody watches. The 7 minutes between clock-in and the first task. The shift that runs 22 minutes long because nobody wanted to be the one to interrupt. The break that stretches. Multiply one careless minute across a crew and a year and it stops being a rounding error and starts being a real line item you’d notice on your P&L.

Here’s what I’d tell that shop owner if he asked me today: stop treating hours as a feeling and start treating them as data. That’s the whole job of time and attendance software, and if you’re still running this on paper or a spreadsheet, you’re the last person in the room who trusts a guess over a record.

The Payroll Gap Map: Where Your Money Actually Leaks

I built a simple model for tracking this a few years back, and I call it the Payroll Gap Map. It splits every hour you pay for into three buckets. The first is productive time, the work you hired someone to do. The second is ghost time, paid minutes that produce nothing measurable, lunch runovers, late starts, and the slow drift at end of shift. The third is unpaid effort, the overtime nobody logged, the early login from the parking lot, the “I’ll fix it later” that never gets reimbursed.

Ghost time and unpaid effort are both expensive, but they pull in opposite directions. Ghost time inflates your payroll. Unpaid effort erodes trust, and it’s the quiet reason your best people eventually leave. Most managers only see one of them because their system only records one of them.

When I first started mapping this, I assumed ghost time was a discipline problem. I was wrong. It’s an information problem. If your crew doesn’t know their exact hours are visible to them, they treat a few minutes as a rounding courtesy. The moment they can see their own clock data, the behavior shifts on its own. You don’t have to chase it.

What a Real Time Record Looks Like

A legitimate time record isn’t a punch-in number. It’s a story about a day. You want the raw clock event, the break markers, the project or job code attached, and the approval trail showing who signed off and when. That’s four layers, and paper gives you roughly one and a half of them.

Digital records also create something a spreadsheet can’t: a trail you can audit. Labour law across most of the developed world sets baseline employee protections around working time, rest breaks and record keeping, and employers are expected to keep accurate records of hours worked.

The European Union publishes its working time directives as an example of how formal these expectations have become. Your own jurisdiction will differ, but the pattern is universal: the burden of proof sits with the employer, not the employee. When a dispute lands on your desk, “I’m pretty sure he was here” is not a defense. A timestamp is.

Why Your Best Employees Hate Your Current System Most

This is the part that surprised me when I ran my first paid pilot with a crew of 22.

The hourly staff whose hours were always recorded correctly were the least bothered by paper timesheets. They clocked in on the minute, clocked out on the minute, no friction. The people who hated it were the ones who actually carried the extra weight. The shift lead who covered a gap and forgot to write it down. The administrator who did 40 minutes of catch-up on a Sunday because she cared. They were being quietly punished by a system too blunt to see them.

So if you’re weighing whether to move off paper, here’s the test I’d run before you buy anything. Take one full work week. Ask each team member to log their own hours twice a day, once at midday and once at end of shift, in a shared sheet. Compare that to the official record. Three things will surface. Who consistently under-reports. Which departments drift most. And whether the drift tracks a real workload problem or just loose supervision. That single week will tell you more about your business than a quarter of reports.

Only then should you pick software. The tool has to fit your reality, not the other way around. A restaurant with a rotating roster needs schedule-driven tracking. A construction company working at multiple sites needs location-aware clocking. A distributed office needs flexible-hour logic. If your team runs on annualised hours or a Bradford-style absence model, your tool has to speak that language natively or you’ll spend the first year fighting it. That’s the kind of thing you should confirm before you sign a contract, not after.

What the Research Actually Says About Presence

The instinct is to assume paid hours and productive hours track one to one. They don’t. We’ve had decades of evidence on the gap between time at work and time actually working, and the pattern holds across industries and countries. SHRM is a solid starting point if you want a neutral clearinghouse on workforce time, engagement and productivity research. The consistent finding is that manager oversight quality matters more than the number of hours scheduled.

Which is the case for the software in the first place. A time system doesn’t manage people. It removes the ambiguity that lets people manage themselves badly, and it removes the blind spot that lets good people go uncredited. Your supervisors still do the human part.

The Tuesday Afternoon Test

If you want a one-minute diagnostic right now, run this. Pull last Tuesday’s records for any single department. Look at the five minute block after every scheduled start time and the five minute block before every scheduled end time. Count how many entries cluster in those windows. If more than two-thirds do, your people are clocking around the edges of what you asked for. That’s your gap. It doesn’t need a consultant to explain it, just a shift in how you measure.

None of this requires you to become a surveillance boss. That’s the move I’d warn against most. Treating your crew like suspects burns trust faster than ghost time ever costs you. The right posture is transparency in both directions: they see their hours, you see the patterns, and the conversation is about workload, not guilt. Half the “problems” I’ve helped owners untangle were just people trying to do a good job inside a system that never gave them the information to do it cleanly.

Stop paying for the hours you think you got. Pay for the ones you can prove. Start with last Tuesday. What does your five-minute window tell you about your own team?