Everything started with a talking script. Once I knew what the video needed to communicate, I'd write the script by hand and build a shot list right alongside it. The two grew together. If I was writing the part about logging in, I'd make a note in the shot list to get a clean capture of the login screen. Script on one side, the shots I needed on the other.

Then I'd send that script to a voiceover artist I worked with regularly. This is the part people are surprised by. It wasn't expensive. Maybe $100 for a two-minute script, and I was really happy with the results. He had the voice, he had the studio, and he did this for a living. For a hundred bucks, it added so much to the production value.

When the VO track came back, I'd record my screen. I'd play the track (usually on a slower speed) and drive through the app doing whatever the narration described. Sometimes that was one clean session, sometimes a couple, depending on how many screens I needed and how much I fumbled. Then I'd pull the footage into Final Cut or Premiere for light cleanup. Trimming dead gaps, retiming a section here and there. Nothing heavy. At the end I'd drop in a logo bumper I'd built in After Effects for the distributorship.

That was the whole thing. Script and shot list, voiceover, capture, light edit, logo. The order mattered, and it still does.

Start with the script. I don't stare at a blank page anymore. I'll talk through the goal of the video the same way I'm talking to you here and get a solid first draft back in a couple of minutes.

There's a better trick I've started leaning on, though. Instead of writing anything first, do a rough run of the demo and narrate it out loud as you click, like you're showing a coworker over their shoulder. Screen record that scratch pass and don't worry about it being clean. Then hand the transcript to an AI like Claude and ask it to turn your rambling into a tight talking script and pull a shot list out of it. Because you narrated what you were doing, the AI can read off which screens you moved through and build the shot list from that. You get the script and the shot list out of one messy pass, which is a lot easier than composing both from a blank page.

Whichever way you start, I don't ship the AI's draft as is. I run it through Humanizer (a Claude skill) so it sounds like us and not like a robot read the manual. The AI gets you off zero. You still do the shaping.

Voiceover is where that client question comes in. You've got three real options, and they're for three different situations. Your own voice when personality matters and you want people to know it's you. A pro when it's going in front of the market and needs to be polished. And ElevenLabs when you're short on time or budget. For natural-sounding narration that's fast to revise, ElevenLabs is a good fit. The revise part is underrated, too. Change one line of script and you regenerate just that line, instead of booking another recording session.

ElevenLabs will also clone a voice. You give it one to five minutes of audio for a quick clone, or a longer clean recording for a better one. For walkthrough videos specifically, a clone of your own voice is a pragmatic middle ground. You keep a consistent sound across a whole library of videos, and you can patch a changed line without setting everything up again. I'd still want a real voice on anything where the personality is the point, but I like the idea of cloning myself for the routine stuff.

For capture, I use Screen Studio, and I'd honestly use it for almost everything if I could. It zooms in on your button clicks on its own, highlights the part of the screen you're pointing at, and it'll mask confidential info or a logo when you need it to. That removes a whole category of manual keyframing that used to eat my time. I run my mic through Krisp while I'm at it, because its virtual mic does a scary good job of making a normal room sound like a studio.

You'll almost always want a light edit at the end. On my most recent video I stayed in Screen Studio for the capture but dipped into Premiere for some finishing tweaks and timing. That's normal. Premiere and Descript both do text-based editing now, where you edit the video by editing a transcript of it. Delete a sentence in the text and the matching video comes out with it. For the light trimming and gap-cutting I described earlier, that's a real time saver.

Last piece is the logo motion at the end. I built those in After Effects, but most distributors don't need to. Go to Envato, find a logo animation you like, drop your logo in, done.

AI speeds up making each piece. It doesn't change the order you make them in.

I've tried to shortcut that order, and it doesn't work for me. What I really want is to record the voiceover and capture the screen at the same time, but I can't do both well at once. Reading a script off the screen while driving the mouse and paying attention to what the app is doing is genuinely hard. I have a teleprompter, and it doesn't solve this, because when I overlay the script on top of my screen I can't click the applications behind it. The teleprompter swallows the clicks. That's an OS limitation, not a me problem, and I haven't found a clean way around it.

So I do what I always did. Run the framework in order: script, shot list, VO, capture, final edit. Separate steps, one after the other. AI just makes each step faster to produce.

Hello Promo is a small promotional products company based in Columbus, Ohio, with a team of three to four people. They sell through an e-commerce website, which means their customers are browsing and buying without a salesperson nearby to help them find what they're looking for or answer questions.

A small e-commerce team can't staff a live chat window around the clock, but customers still expect quick answers. Hello Promo needed to support shoppers at any hour without adding headcount.

A few specific things had to work:

PromoPilot looked at what Zoho SalesIQ's Zobot platform could do against what Hello Promo actually needed. The shopping assistant was the trickiest piece: the bot had to understand a customer's intent from a freeform question, call the product catalog API, and return results in a format that works on a website, with images, prices, and clickable links.

Zoho SalesIQ had the AI capabilities and API integration flexibility to make that work. Zoho Desk was already part of Hello Promo's setup, so connecting ticket creation to the bot's escalation path was straightforward.

PromoPilot built a Zobot on Zoho SalesIQ with three conversation modes:

The build took about a month. Most of that wasn't plumbing the integrations but tuning the prompts: getting the AI to reliably read customer questions, route them to the right path, and respond in a way that felt natural. Shopping queries took the most iteration, since customers phrase questions about sizes, colors, and availability in a lot of different ways.

The product catalog API integration and Zoho Desk ticket creation were built alongside the prompt work and tested against real customer scenarios before going live.

That's already north of $45k, and it doesn't include your own team's time on sales, account management, and accounting. Pinning down the exact overhead on any one program is hard, because most of these resources are shared across many stores rather than dedicated to a single one. But do the math even roughly and you'll often find the net profit on a program isn't what the gross made it look like. Set the store up as a free perk that rides along with the order, and every one of those costs comes straight out of your margin, invisibly, month after month.

You can't price a program you haven't costed, and it's easy to run a store for years without ever stopping to do it.

When we're working with suppliers in commonsku, there are times we want that supplier information available in Zoho CRM as well.

We built a custom button that takes the supplier information from commonsku and sends it directly into Zoho CRM. What used to involve copying and pasting between two systems is now a single click.

We added another button that syncs contact information from commonsku to the matching contact in Zoho CRM. Before making any changes, PixieBrix displays a comparison window that shows the existing CRM data alongside the updated information from commonsku.

That gives the user a chance to review everything, make edits if needed, and confirm the update before anything is written to the CRM. It's a small touch, but it gives everyone confidence that the automation is doing exactly what they expect.

We also built a browser mod that reads information from a commonsku sales order and uses it to fill out an inventory receiving log automatically.

Instead of manually copying order details into another system or spreadsheet, PixieBrix gathers the information for us and starts the process with a single click.

It's one of those automations that only saves a few minutes each time, but when you repeat that task throughout the week, those minutes add up.

I've always enjoyed finding ways to automate the repetitive parts of work. Sometimes with Zapier. Sometimes with AI. Sometimes it's a custom app.

Lately, PixieBrix has become another favorite because it fills a different niche. Instead of connecting systems behind the scenes, it improves the experience of the software I'm already using.

I no longer assume that every missing feature has to stay missing. If there's something that would save a few clicks, reduce copy-and-paste, or bring information together in a better way, there's a good chance we can build it ourselves.

That's a fun way to think about software.

Most automation conversations in promo start with the easy wins: syncing orders, pushing data between your CRM and your ERP, triggering a Slack alert when a payment posts. Eric covers a lot of that ground on this blog, and for good reason — those Zaps save real hours every week.

But there's one part of the order that almost everyone still does by hand: the artwork.

A customer uploads a logo. Someone on your team opens it, squints at the resolution, redraws it if it's a JPG pulled off a website, drops it onto a product mockup, sends a proof, waits for approval, fixes the placement, sends another proof, and finally exports a production-ready file the decorator won't bounce back. Multiply that by every line on every order, and the "creative" step quietly becomes the most expensive, slowest, most error-prone part of your operation.

Think about what a single proof actually costs. It's not just the few minutes of design time. It's the email thread. The "can you make the logo bigger" reply that lands two days later. The version that goes to production with the wrong Pantone because someone eyeballed it. The reorder that doesn't match the first run because the setup lived in a designer's head instead of a system.

None of that shows up cleanly on an invoice, which is exactly why it's so dangerous. It hides in turnaround time, in rework, in the orders your team can't take on because they're stuck shepherding proofs for the orders they already have.

Artwork automation is the idea that everything between logo upload and production-ready file can be handled by software, with specs built in, instead of by a person checking each step manually.

In practice that means a system that:

That last point is the one most people miss. When the proof is the production file — not a pretty picture that someone re-creates later — an entire category of "the print didn't match the proof" errors disappears.

Those gains aren't theoretical. For one large print platform, Helloprint, automating artwork across 30+ product categories cut production time by 80%.

The conversion number deserves a second look, because it reframes the whole thing. Proofing isn't only a cost center to be trimmed — it's part of the buying experience. A buyer who sees their logo on the product, rendered accurately, in the moment they're deciding, is a buyer who's far more likely to check out. Speed on the back end and conversion on the front end turn out to be the same investment.

If automating artwork were just "slap the logo on a mockup," every storefront builder would already do it. The reason it's genuinely hard is that promo is a specs business. A mug has a wrap area and a safe zone. A polo has a stitch count and a thread palette. A pen has a print window measured in millimeters where a logo either fits or it doesn't.

Automation only works if those constraints live inside the system. That's why the foundation matters more than the front-end editor: at FastEditor we maintain 500,000+ production-ready product configurations built on real specs from 140+ suppliers, so the output respects each product's actual decoration rules. The decoration method matters too — screen print, DTF/DTG, embroidery, laser engraving, deboss, UV, sublimation, and pad printing each behave differently, and the simulation has to reflect that or the proof is lying to the customer.

Get the specs right and the magic works: the proof is trustworthy, the file is clean, and nobody downstream has to fix anything. Get them wrong and you've just automated the production of bad proofs.

1. Measure your current proof cycle. How many minutes of skilled time per order? How many proof rounds before approval? How often does production kick something back? You can't improve what you haven't timed.
2. Pick one high-volume product category — apparel, drinkware, or pens are common starting points — and automate the proofing there first.
3. Make the proof the production file. This is the single change that removes the most rework.
4. Then connect it to the workflows you've already built. This is where the rest of PromoPilot's playbook comes in: once artwork generation is automated, you can trigger it, route it, and sync it like any other step in your stack.

Every distributor gets to this question eventually. Do we stay on software built for promo? Or do we move to a broader ERP?

If you own the business, this is bigger than a tech purchase. You are deciding how work moves through the company. You are deciding whether growth creates leverage or simply creates more administrative work.

The real issue is operational friction. Teams spend enormous amounts of time copying data between systems, cleaning spreadsheets, chasing approvals, re-entering orders, fixing bad syncs, and answering questions that software should already know the answer to. A little friction is manageable. At scale, it becomes expensive.

And scale is exactly what many distributors are chasing. ASI reported that North American promotional-products distributor sales reached a record $27.7 billion in 2025. PPAI reported continued growth across the industry. But growth alone does not create healthy operations. In many cases, rising revenue simply exposes weak systems faster.

I keep coming back to the same conclusion: the future belongs to operators. The companies that scale well are the ones that pair strong sales with disciplined systems, clear processes, and intentional automation.

When I say niche software, I mean industry-specific platforms like commonsku, Antera, and MPower Promo. When I say enterprise ERP, I mean broader systems like Zoho One, NetSuite, Odoo, and Business Central.

Niche tools are purpose-built for promo. Enterprise tools are broader foundations that you shape around the business. One gives you more out of the box. One gives you more room to define your own roadmap.

That is the cleanest way I know to frame it. After this point, I am going to keep it generic, because the bigger issue is how these categories behave once your business starts to grow.

This decision mattered five years ago. It matters more now.

PPAI reported that online promo sales reached $6.83 billion in 2024, representing 25.5% of total industry sales. The same report found that 84% of large distributors and 60% of small distributors were selling online. Online inventoried company stores alone generated $2.35 billion. Ecommerce is no longer a side channel. For many distributors, it is core infrastructure.

At the same time, the work itself is becoming more complex. PPAI reported that $4.3 billion of distributor sales came from non-industry providers, while retail branded products accounted for another $5.3 billion. Distributors are sourcing from more places, supporting more program types, and managing more exceptions than they were a decade ago.

That is where software starts to matter in a very practical way. The platform underneath your business either helps absorb that complexity or pushes it back onto your team through manual work, disconnected systems, and operational overhead.

I completely understand why owners choose niche software. It already speaks the language of promo. Many of the odd operational realities of this industry are supported from day one. Supplier workflows make sense. Common program structures are familiar. The team usually needs less translation and less customization to get moving.

That simplicity has real value. Most owners do not want to spend the next nine months in software workshops defining fields, approvals, and workflows from scratch. They want the team trained. They want orders moving. They want a faster path to operational stability.

For many distributors, that is exactly the right choice. If your workflows are relatively standard and your growth does not depend on highly custom operational processes, industry software can be a very strong fit. I do not see that as settling. I see it as pragmatic.

There is also a human side to this decision. Panorama found that fewer than one-third of organizations intensely focused on change management during ERP projects. That matters because even good software can fail if the rollout overwhelms the team. Simpler systems often reduce that implementation burden significantly.

The tradeoff usually shows up later.

Niche tools can feel tailor-made to your business until the work becomes more complex. I usually see the tension emerge when distributors move deeper into ecommerce, large company-store programs, redemption workflows, or custom client experiences. The operational edge cases start piling up quickly, and the standard lane begins to feel narrow.

There is also a differentiation challenge here. When you use the same supply chain and the same operational software as everyone else, you have to work harder to explain why the client should choose you. Some distributors solve that through exceptional creativity. I think of The Icebox here. Plenty of distributors talk about creativity, but very few execute graphic art and brand design at their level. Others differentiate through technology, logistics, or operational sophistication. Either way, the point is the same: you have to become intentional about where your value lives.

The other issue is roadmap dependency. When you adopt a platform, you are also adopting its priorities. If the vendor's roadmap aligns with your business, that can work well. If it does not, you wait. And while you wait, opportunities can pass by.

That is the hidden cost I think about most. Not inconvenience. Missed capability. A team saying no to work they could probably win because the current system cannot support it.

Integration flexibility matters too. I always want to know how easily a platform communicates with the rest of the stack. Native integrations help. APIs help. Webhooks help. Closed systems usually push the operational burden back onto employees through spreadsheets, manual re-entry, and workaround processes.

Enterprise systems appeal to owners for a different reason: they give you more control over how the business operates.

If your company wants to expand into new service lines, support unusual workflows, or build more custom operational processes, enterprise platforms usually provide more room to do that. Promo-specific systems were largely designed around physical products and traditional distributor workflows. That works well until the business starts moving outside those assumptions.

I often think about service-heavy work here. Media buying, creative retainers, kitting programs, warehousing services, managed storefront programs, or recurring operational fees do not always map cleanly to traditional promo pricing structures. Broader ERP platforms are often better equipped to model those kinds of operational and financial relationships.

There is also a continuity argument that I think matters to owners. Larger ERP ecosystems typically come with broader implementation networks, deeper integration ecosystems, larger developer communities, and more long-term platform investment. From a buyer-confidence standpoint, that matters.

And "enterprise" does not only mean giant corporations. Panorama places Lower Tier II ERP buyers at $10 million to $250 million in revenue. That is a useful reminder for distributors. This conversation often applies squarely to the middle market.

The cost is real. The timeline is real. The decision load is real.

Panorama found a median ERP project cost of $450,000 and a median timeline of 9 months. This is not a casual software purchase. You are making decisions about workflows, approvals, reporting structures, data ownership, permissions, and operational logic. Some leadership teams are energized by that level of control. Others find it exhausting. I think it is important to be honest about that up front.

The implementation partner matters just as much as the platform. I strongly prefer partners who understand promotional products operationally, not just technically. Outside firms often miss nuances our industry considers obvious.

Inventory ownership is a good example. Just because inventory is physically sitting in a distributor's warehouse does not mean the distributor owns it financially. You can have one order where one line item creates revenue to the distributor while another line item on that same order generates a payable or rebate back to the client. If the implementation team does not understand those distinctions early, accounting logic can become unstable very quickly.

The same pattern shows up in data quality. Panorama found that data integrity and consistency issues were the most common reason ERP projects exceeded schedule, while unexpected technical requirements were the biggest reason budgets expanded. That tracks closely with what I see. Companies often blame the software first, but the real bottleneck is usually upstream in the process design or the data itself.

This is also the stage where some owners start considering custom software. I understand the appeal. But building software and operating a distributorship are very different businesses. Unless custom development creates a genuine competitive advantage, I usually believe distributors should exhaust strong off-the-shelf options first.

This is the step I wish more companies would take.

Before I recommend changing platforms, I want to know whether the current system has actually been pushed to its limits. A surprising amount of operational pain comes from inconsistent processes, unclear ownership, undocumented workflows, or work being split awkwardly across teams.

I use the word deterministic a lot. What I mean is that a process has clear, repeatable inputs and outputs. If a task is repetitive, frequent, and predictable, it deserves a close look. That is where automation and process design tend to create the most leverage.

I recently untangled a tax liability workflow that was spread across half a dozen spreadsheets. At first glance, it looked like a software problem. Once I traced the workflow end to end, I realized the real issue lived upstream in how the data originated and moved through the organization. Once we identified that, the solution became much clearer.

That is why I keep coming back to process clarity before automation. If a workflow is inherently inconsistent, overly subjective, or missing ownership, automating it usually just scales the confusion.

I also see companies paying for platforms they barely use. The system may already have APIs. It may already support integrations that nobody implemented. Often the real blocker is organizational hesitation, not technical limitation. "We have always done it this way" and "What if it breaks?" are understandable concerns, but they are usually change-management problems, not proof the software itself has failed.

A full platform switch is not the only move.

In many cases, the better answer is to solve the immediate operational pain with a focused integration or workflow and buy the business more time. That is usually how I approach these situations. I look for native capability first. If that is not enough, I look for a flexible automation layer. Only after that do I start seriously discussing a larger architectural change.

I once helped keep a client on their existing company-store platform by building a custom workflow that recreated functionality they were about to leave for elsewhere. We captured order data, used line-item metadata and custom flags to control logic, and triggered downstream processes even though the platform lacked a clean native API path. That kind of bridge solution can be extremely valuable. It allows the business to keep moving while leadership decides whether the larger platform still fits long term.

When a system is especially closed, I will even use scheduled reports or email-based triggers to move data downstream. It is not glamorous, but it can still be reliable and effective.

If you take this approach, ownership matters. Build workflows in an environment the company controls. Assign clear responsibility for monitoring and maintenance. Avoid shared logins for critical automations because they blur accountability and make troubleshooting harder. I also strongly prefer automated alerts and summary notifications so failures are visible quickly instead of quietly sitting unnoticed for months.

Software decisions fail when leaders ignore the people side.

If Sally is in sales, I want Sally selling. If Sally is also the only person who understands a critical operational workflow, the business has a continuity problem. Important processes cannot live entirely inside one employee's head.

At the same time, the people doing the work are often the best source of operational truth. They know where the exceptions live, where approvals break down, and where human judgment still matters. That is why I strongly prefer involving operations, accounting, and frontline staff early in process mapping and discovery work.

I also do not buy the idea that automation eliminates the human side of business. McKinsey estimated that fewer than 5% of occupations could be fully automated with demonstrated technologies, while roughly 60% contained activities that could be partially automated. That aligns closely with what I see in practice. The goal is usually not replacing people. It is removing repetitive operational work so people can focus on judgment, service, creativity, and relationships.

Long term, I like seeing operational capability develop inside the business itself. I am a big believer in citizen developers and internal process owners. That is one reason I prefer building workflows inside the client's own environment whenever possible. I want the company to own the system and continue evolving it over time, even if that eventually means they need outside help less often.

I can make the case for both paths because both paths are valid.

If your workflows are still relatively standard, your team wants faster time to value, and you do not require a high degree of operational customization, industry-specific software can serve you very well for a long time. If your growth depends on advanced ecommerce, sophisticated redemption workflows, broader sourcing models, or service lines that stretch beyond traditional distributor operations, enterprise platforms deserve serious consideration.

I do admire the flexibility of enterprise systems. They give distributors more room to define how the business operates and evolves over time. At the same time, I would not push every distributor in that direction. Many companies will perform better with a strong industry platform that they have fully learned, integrated thoughtfully, and supported with disciplined process design.

So if you are trying to make this decision, start with the business you are actually trying to build. Look at where margin is leaking. Look at where your team spends time on repetitive operational work. Look honestly at whether your current systems support the type of business you want to win next year, not just the business you won last year.

Choose the path that gives you room to scale, keeps your people focused on high-value work, and allows the business to say yes to the right opportunities.

That is the real software decision.

Useful wins more often than clever.

ASI found 78% of consumers keep a promotional item because it is useful to have. That should shape what you recommend. If the product has no real place in somebody's life, the campaign has to work much harder.

This is one reason apparel, bags, and other visible items keep doing well. ASI estimates fleece and jackets generate about 9,000 impressions over their lifetime, while bags generate 4,900 and caps 4,000. People wear them. Carry them. Set them down in front of other people. The product keeps doing work after the invoice is paid.

Promo also moves perception. ASI found 76% of U.S. consumers said they would be more likely to do business with an advertiser after receiving a promotional item, and 78% said they would have a more favorable view of that advertiser. Those are not small numbers.

The item should create a moment. As your client's merch expert, you have the opportunity to help that moment continue.

That matters a lot at events. PPAI says 75% of consumers agree promotional products received at events make the experience more memorable. Great. Now give that memory a next step. Send them somewhere. Ask for something simple. Offer something useful. Capture the engagement.

The same logic applies to direct mail. USPS found advertising mail sent to existing customers was 64% likely to be read and had a 25% "very likely to respond" rate. If your client is mailing current customers, that is a real opportunity. Tie the piece to a tracked landing page or pURL, or a digital destination and you have a much stronger story to tell.

A lot of discovery in promo starts too low. People jump straight to the product. They ask about budget, timeline, and colors before they ask what the client is actually trying to make happen.

I would start higher.

Ask what the recipient should do next. Ask what behavior the client wants. Ask what would make the campaign feel successful three weeks later. If you start there, product choice gets easier and the digital pieces make more sense.

If the goal is employee onboarding, the next step may be a repeatable onboarding experience tied to new hires. If the goal is event follow-up, the next step may be a landing page with a clear call to action. If the goal is awareness with proof, the next step may be a tracked QR code that shows traffic and conversion.

You do not need technical jargon to sell any of this.

If you are talking to HR, say, "We can make it easy for your team to send store credit without emailing us every time." If you are talking to marketing, say, "We can give you a simple scan so you can see who engaged and what they did next."

Focus on the outcome. If they ask about a feature, then map a solution you already know and solve for to an outcome. That keeps the conversation clear.

I also think reps can hurt themselves when they rush discovery. When that happens, you risk misalignment between what the client expects and what you're really offering. That is how uncomfortable conversations show up later. I would much rather slow down the sales process, but be aligned with what the customer is expecting and what we can deliver, than quickly jump to a contract that we can't fulfill.

This is one of the biggest misses I see in our industry.

Reps will work hard to win the merchandise order, then give away the service side to make the deal feel easier. They toss in the company store. They toss in the redemption site. They toss in reporting. Then the team spends a lot of time building and running all of that work for free.

That creates two problems. You train the customer to think the service has no value. And you leave real revenue on the table.

I have spent years building company stores and e-commerce programs. They take planning, setup, content, testing, and maintenance. There is real work there. The same goes for digital asset services and campaign reporting. If you bury all of that effort inside the product margin, you create an operational margin drain.

A lot of reps are comfortable selling products because the pricing is coded and familiar. There is a margin. There is a process.

Service work is different. There is no coded pricing for many service-related SKUs.

I felt that myself early in my career when I was working on a direct mail campaign with an augmented reality component. The physical item was simple. The heavier lift was the digital experience behind it. There was no clean industry formula telling me what that service should cost. I did some research, then came up with a number that sounded right.

That discomfort is one reason reps underprice service or give it away. Sometimes there is also fear that if the service price feels too high, the client will walk away from the product order too. In some shops, reps also are not commissioned on services the same way they are on products. I understand why that creates hesitation. It still does not make the free labor any healthier.

My advice is simple. If an off-the-shelf solution exists, you should prioritize it.

Most promo shops shouldn't build custom software. You will face high costs and constant headaches. That excitement over a custom system fades fast.

It is easier to sell a solution that has been well-defined than something fully custom. If you have the right tools and partners, you can explain the offer clearly. Your team knows how to deliver it. Your client knows what they are buying.

Bring your operations and e-commerce people into discovery early. They need to be in the room. They help you define what is realistic before the promise gets made.

Turn the Product Into a Digital Next Step

I know "phygital" sounds like industry jargon. Let's keep it simple: a physical product triggers a digital action.

That next step might be a landing page, a company store, a video, a redemption page, or a form. The point is simple. The product starts the interaction, then something measurable happens after it. This does two things for you and your customer:

1. It proves that branded merch can drive behavior.
2. It provides the brand with an opportunity to extend the brand experience from the physical realm into the digital.

This is where a lot of reps leave value on the table.

A QR code that goes to the homepage is fine. It is better than nothing. But you can get much more useful information if you add tracking to the link.

Google's own guidance says to always use utm_source, utm_medium, and utm_campaign. In normal language, that means the client can look at their website data and tie the visit back to the exact item or campaign that drove it.

Now the postcard, kit insert, event badge, catalog, or giveaway is not just a nice touch. It becomes part of a measurable campaign. And when you help the client do that, you position yourself as a solution partner who is outcome-oriented and not solely focused on the product itself.

If this sounds technical, don't worry. Your client's marketing team should be able to simply provide you with the URL the QR code should link to. All you should need to do is bring it up if your buyer doesn't. Worse case scenario, they have no idea what you're talking about but you've proven that you think beyond the product sale.

Once the campaign is live, bring back something useful.

Show traffic to the digital destination (if your team built it). Show how often the call to action converted. Show heat maps if you have them. Show top-moving products, bottom-moving products, and categories that are underserved. That review changes the whole tone of the conversation. You are not guessing whether the campaign worked. You are reviewing what actually happened.

If you are selling your first tech-enabled experience and you want a safer starting point, I like partners like Outgage. They can help reps with both the digital destination and the reporting. That lowers the risk and makes the offer easier to explain.

The best service offerings are the ones clients immediately understand.

A company store that lets HR send onboarding gifts without emailing customer service every time solves a real problem. A redemption experience tied to an event creates measurable engagement. Reporting that shows what happened after a campaign gives the client something useful to act on.

Your operations and e-commerce teams matter here. Don't forget to bring them into discovery early so the promise matches what can realistically be supported.

The goal is not to become a software company. The goal is to make branded merch easier to execute, easier to measure, and more connected to business outcomes.

Promotional products still earn attention because they are useful, visible, and memorable. That part is not going away.

What changes now is the layer you put around the product. Sell the outcome. Charge for the service work. Give the item a digital next step. Track what happens. Keep the offer simple enough for your team to support. Bring operations in early. Use simple workflows that your team can actually support.

The future belongs to the operators. I believe that more every year.

And if you are a sales rep, that should encourage you. Better systems do not take away your human touch. They give you more time to use it. Let the tools handle the repetitive and frequent or annoying work. You go build trust, solve problems, and sell more. 😊

For a long time, company stores have done a pretty narrow job. They help clients buy branded merch, apparel, and printcollateral. They support uniform programs, safety programs, employee recognition, and basic purchase control.

That job still matters. I'm not dismissing it. But I do think the definition is already too small for where clients are headed.

I spent 13 years on the distributor side building e-commerce and company store programs. Most of them looked the same. Then one enterprise client forced us to rethink what a company store could actually be.

Modern clients are moving away from fragmented vendors, seeking instead a centralized, frictionless brand management portal that integrates physical swag with digital assets and marketing collateral to ensure a unified presence.

If your store only handles the mug and the polo, the client still has to leave that environment every time they need something more strategic. There's an opportunity here for promo distributors to offer something powerful and unique.

The market is telling us this shift is real. Cloudinary cites research showing that 93% of B2B marketers use content marketing as a core strategy and about 39% of marketing budgets go to content creation. Capture a slice of that budget to unlock a fresh revenue stream.

Demand for asset management is growing fast too. The global DAM market is projected to reach $10.9 billion by 2029. That tells me clients want one place to control brand assets, approvals, and distribution. They do not want brand files floating around in five systems and fifteen inboxes.

This is not a future trend. Clients are already reorganizing how brand work gets done.

We were trained to think like sellers. Win the account. Pitch the product. Fill the order. Move to the next opportunity.

But the future company store is not a sale - it is a system that embeds itself inside your client's business.

That shift creates a real challenge for sales teams.

Most reps in this industry are trained to sell products with clear, coded pricing. A mug has a cost. A polo has a margin. You quote it, you move on.

Services do not work that way.

Digital asset management, media personalization, direct mail execution - these are not line items with standard pricing grids. They require scoping, judgment, and often ongoing support. That is uncomfortable if you are used to quoting from a catalog.

If you do not adapt to that shift, you will either avoid selling these services or give them away. The shift is simple: you are no longer selling products, you are selling outcomes.

I think the winning store program of the future becomes a front door for brand execution. It still handles merch, apparel, and print. But it also gives client employees a clean place to access approved digital assets, request direct mail, launch social campaigns, kick off advertising campaigns, media buying – whatever a marketer could need. A holistic brand management portal. In other words, the store becomes infrastructure.

What do your store users, especially marketing teams, need to do today? They may need to order tees for an event, grab approved social graphics for the event, execute a direct mail drop, and send a a gift to event speakers.

That is where the store gains massive utility by centralizing requests, enforcing standards, capturing data, and initiating workflows. The best stores stop being catalogs and start becoming systems.

Years ago, one of our largest clients invited us to a demo.

The problem was, it was not our platform. 😬

They were evaluating a platform that looked less like a traditional e-commerce store and more like a brand management and execution system. It handled digital asset management, personalization, and campaign execution - but it could also support e-commerce for physical products.

That was an "oh shit" moment.

It made one thing very clear: the client's expectations had already moved, and we were behind them.

Inviting us to that demo was their way of saying, "This is what we want." One place where their franchisees could get everything they needed to run the business - physical and digital.

We had two options. Defend what we had, or close the gap.

We closed the gap. We had to.

That same client pushed us into some of the most practical builds we ever did. They asked for dynamic video rendering that mirrored the logic we were already using for variable data print. Same idea, different medium. Our platform did not support it natively, but it was flexible enough that we could make it work.

We also built a social media asset customization and management workflow inside the store. At that point, the store was not just processing product orders. It was helping execute brand activity.

That is when it clicked. The store was no longer a catalog. It was infrastructure.

This shift changes the business in a few important ways.

First, it makes you harder to replace. If you are only fulfilling orders, you are easy to swap. If you are embedded in how the brand operates, you are not.

Second, it expands your revenue surface area. You are no longer limited to product margin. You can charge for access, support, and ongoing execution.

Third, it forces pricing discipline. Most distributors do not lose margin on product. They lose it on unscoped service work. This model forces you to define and price that work clearly.

Traditional promo sales teams are excellent at selling physical products. They know how to price the mug, the polo, and the banner.

Service work is different.

There is no standard grid for digital asset management, campaign execution, or workflow support. You cannot quote it the same way you quote a product.

That creates hesitation. Reps either avoid selling it altogether or treat it like a throw-in to win the deal.

That is where margin disappears.

If your store is helping manage assets, execute campaigns, or run workflows, you are delivering real operational value. That work should be priced accordingly.

There is no single formula, but there are a few practical models that work:

• Platform or access fee
  Charge for access to the system itself. If the store is acting as a brand portal, that has standalone value.
• Workflow or service fees
  Charge for specific capabilities like asset management, campaign execution, or direct mail coordination.
• Ongoing support or management fees
  If you are maintaining the system, supporting users, or managing requests, that is recurring work.

The mistake is trying to hide this inside product margin. That model breaks as soon as service work becomes a meaningful part of the offering.

Merch still matters. Apparel still matters. Print still matters.

But that is no longer the whole job.

The company store is evolving into the place where brand work actually happens. Where requests start, rules are enforced, and execution gets triggered across channels.

The distributors who win will not be the ones who sell the most products. They will be the ones who own the outcomes.