Donovan Brown

The same habit shows up across a payment-setup session with a business owner, a coaching session on a custom CMS and a Shopify project: cut jargon, repeat concepts, break the work into smaller pieces and adjust to whoever is listening. On the Shopify project, they note that the project manager does not come from a technical background, so updates stay clear and jargon-light to keep the project moving in the right direction.

A small-business owner running an e-commerce site did not understand how payment processors work.

• Donovan Brown describes repeating concepts, using less jargon and explaining things as straightforwardly as possible.
• They admit slipping into a jargon term once, then quickly correcting it.
• The owner eventually grasped the fundamentals.

Read original · Original 2 · Original 3 · Original 4

Even at the most sensitive moments, the safer and more respectful move is to have the owner handle their own credentials while they stay out of the way.

When an account would not sync with a business bank account, Donovan Brown describes diagnosing the exact issue, asking the right questions and guiding the owner as she took control, entering her own sensitive information while they discreetly looked away. The session ended with the owner seeing a "successfully connected" message in her admin panel.

Read original

The point is practical: when neither party has used a system before, probe how it is wired together, then transfer that understanding to the client.

A client who sells an alcohol-free alternative to traditional hand sanitizers was uncomfortable updating his site.

• It ran on a custom CMS neither of them had used, rather than WordPress or Shopify.
• Donovan Brown drew on past experience with traditional, headless and custom CMS platforms, tested how the content and navigation were connected, then had the owner make the content and price updates himself while they answered questions.

This slightly qualifies the "apply past experience" claim: in this case the answer was active probing of an unfamiliar admin area, not prior knowledge of that specific CMS.

Read original · Original 2

As lead developer, they work alongside an in-house project manager on sprint planning and launch expectations. The plan is to write custom code or scripts that route visitors back to the original company or product featured on the site, using an off-the-shelf platform to send attention to local businesses rather than only sell directly.

The dev update lists the practical build steps: connecting the domain, adding placeholder and test products to map the site flow, creating core pages, and starting the footer and navigation. Donovan Brown explains that the custom code will point visitors back to the featured company or product as part of the user flow.

Read original · Original 2

A newcomer wondering whether Brown can explain technical setup to someone without that background should start here.

Brown describes a consulting session with a small-business owner who ran an e-commerce site but did not understand how payment processors work.

• They broke the concepts into plain terms, repeated explanations, dropped jargon, and corrected themselves when a jargon term slipped out.
• A bank-account sync problem came down to diagnosing the issue, asking the right questions, and having the owner enter their own sensitive information while they looked away.
• The session ended with the owner seeing a "successfully connected" message and, in their account, hugging them three times.
• The post is a personal narrative, not a case study, and gives no store name, platform names, timeline, or measured outcome.

For brands planning a campaign

For agency work involving payments or account setup, point to this pattern: explain, diagnose, then let the client handle their own credentials. It supports a contract role where client-facing explanation is part of the deliverable, not a separate training package.

The value is not prior knowledge of a specific CMS, but the ability to probe an unfamiliar admin area and transfer that understanding to the client.

Brown helped a client who sells an alcohol-free hand-sanitizer alternative update prices and content on a custom CMS neither of them had used before.

• The site was not on WordPress or Shopify.
• They drew on prior experience with traditional, headless, and custom CMS platforms, tested how content and navigation were wired together, then switched roles: the owner made the updates while they answered questions.
• Brown says the owner left with the confidence and clarity to manage updates alone, and mentions a thank-you gift from the client's company.
• The post says the platform was unfamiliar but does not name it.
• Ask how long the session took and how the site performed afterward.

For brands planning a campaign

Useful for projects on custom or legacy CMS platforms without documentation.

• It supports positioning Brown on unfamiliar-stack handoffs and client self-sufficiency.
• Ask which specific platforms Brown has worked in.

Read this first to see whether Brown has worked under a client's own process.

Brown is the lead developer on a Shopify build for one of Live6 Alliance's Detroit initiatives, working with an in-house project manager.

• The post reports that development has kicked off, sprint planning is done, and launch expectations are aligned.
• The stated goal is impact for local small businesses.
• This early project announcement establishes the role, organization, and working arrangement.

For brands planning a campaign

Relevant for agencies and initiatives that run their own project management and need a contract developer who fits into sprints and launch planning. The post predates delivery, so treat it as a starting engagement, not a completed reference.

It shows what a week of the work looks like, rather than just stating a job title.

Brown lists the practical build steps completed on the same Shopify site: connecting the domain, adding placeholder and test products to map site flow, creating core pages, and starting on the footer and navigation.

• The platform serves small businesses in Detroit, so they expected to write custom code or scripts that route visitors back to the original company or product as part of the user flow.
• They also note that the project manager does not come from a technical background, so they keep updates clear, avoid heavy jargon, and break things down when needed.

For brands planning a campaign

Useful when a brief calls for a developer who builds in Shopify and writes progress updates a non-technical stakeholder can act on. The planned custom code to route visitors back to a featured company is a concrete indication of the kind of work Brown takes on, but it is a plan, not a demonstrated result.

The work covered sprint planning and launch alignment, then moved into building the store: connecting the domain, adding placeholder products to map the site flow, creating core pages, and starting the footer and navigation.

Working on an off-the-shelf platform while coordinating milestones with a non-technical project manager.

For brands planning a campaign

A fit for briefs that need someone to run a Shopify build end to end, from planning and communication to theme edits. Relevant to platform, commerce, and small-business programs.

Examples: Source 1 · Source 2

They broke down the concepts in plain language, repeated them, and cut jargon, then diagnosed why the account would not sync with the owner's business bank account. The owner entered sensitive details herself while they looked away, and the setup ended with a working payment connection.

Plain-language explanations and guided troubleshooting, with the client performing sensitive steps rather than handing over credentials.

For brands planning a campaign

Useful for fintech, payments, and e-commerce briefs where the audience is business owners rather than developers. The handling of sensitive account details helps preserve client trust during technical setup.

Examples: Source 1

The barrier was confidence, not the product: the owner was not comfortable in the CMS admin area, and the site ran on a custom CMS that neither of them had used before. Brown tested how content and navigation were connected, then had the owner make the content and price updates himself while answering his questions.

Learning an unfamiliar CMS on the spot, then putting the client in the driver's seat for the edits instead of making them on his behalf.

For brands planning a campaign

Speaks to briefs about client enablement and handover, where the goal is a business owner who can maintain the site after the engagement ends. Also relevant to agencies working with client sites on non-standard platforms.

Examples: Source 1

The project is designed to help small businesses in the area, so the storefront is meant to route attention to local companies rather than only sell directly.

Extending a hosted platform with custom scripts when the standard storefront flow does not match the project's goal.

For brands planning a campaign

Relevant when a brief needs more than a stock template: someone who can adapt a platform's customer journey to a program's purpose while keeping the build maintainable.

Examples: Source 1

With the project manager, Donovan Brown avoided jargon and broke down the work so everyone understood the direction.

• With clients, they repeated concepts, corrected jargon slips, and let the client take control of the work.
• They also frame not knowing everything as normal for IT professionals, saying what matters is knowing how to learn, test, adapt, and apply related past experience.

Repeating and simplifying concepts, correcting jargon as it comes up, and pairing explanations with hands-on practice.

In two cases, they tested unfamiliar platforms rather than relying on prior expertise.

For brands planning a campaign

A clear thread for agency work: a contract developer who can explain technical work to a non-technical client, reducing the account and project-management load around the build.

Examples: Source 1 · Source 2 · Source 3 · Source 4

The post describes the work as a side project and says the site is meant to help local small businesses.

View example

The owner gave a hand sanitizer as thanks. The post names the business in a shoutout and says the owner is a client.

View example

Donovan Brown shows a payment setup and CMS handover as they happened; Windorpski explains what to check before spending more on marketing.

Windorpski's posts are advisory and conversion-focused, written from an agency position and ending with a question to the reader. Donovan Brown's are narrative accounts of single client sessions, with the client's own hands on the keyboard.

Read original · Original 2

Ahmed names stores they run on each side of the comparison, while Donovan Brown's Shopify build notes cover the same ground: which platform suits which business, and how the owner will manage it afterward.

Ahmed's posts are marketing-led, with named client sites, portfolio links, checkout methods, and explicit invitations to comment or send a message. Donovan Brown describes individual client sessions with little selling language and no portfolio or store listings.

Read original · Original 2

They treat the platform question as the wrong starting point and redirect it toward what the business actually needs.

Himanshu writes in decision frameworks and tiers, with matrices, cost figures, and strategic framing aimed at a leadership audience. Donovan Brown works from concrete client situations told as short narratives.

Read original · Original 2

Their WordPress-versus-Shopify post opens by refusing the usual question — 'should I build on WordPress or Shopify?' — and replaces it with one the agency can use in a client meeting: what does the business need to do in eighteen months that it cannot do today?

• They name the failure mode agencies slip into (pushing whichever platform the team is most comfortable with) and set out when each platform wins: WordPress for design freedom and content that carries SEO and AI search visibility, Shopify Plus for fast scaling, checkout, and inventory.
• Their other post makes the matching point on traffic: SEO can be working perfectly while the site still loses sales, and they give three checks a client can act on.
• For an agency that needs a contractor to shape the platform recommendation as well as build it, this is directly relevant.

The tradeoff is documented client handoff.

• The posts make arguments and pose diagnostic questions for peers; they do not show someone guiding a non-technical owner through a setup problem.
• Donovan Brown's posts show the exact moment an agency needs covered after launch: working out why a payment account would not sync with a business bank account, then having the owner enter their own sensitive details.
• Windorpski's work shows the recommendation and the reasoning behind it.
• If the agency needs someone to run the after-launch session where the merchant learns the admin, Donovan Brown's posts show that; if it needs someone to defend the platform choice to the client, Windorpski's work does.

Examples: Source 1 · Source 2

Their posts name two working stores and place one on each platform — MYNAH MART on Shopify, Royal User UK on WooCommerce — giving the agency side-by-side proof to show a client weighing platforms.

• Their Shopify-versus-WooCommerce post gives a plain cost-and-flexibility breakdown for each and lands on a practical test for a store the owner can manage: does it load fast on a phone, and can the owner manage it without calling a developer?
• They also build for owners who need payment and delivery handled simply, listing card, bKash, Nagad, and Cash on Delivery checkout, and they work with businesses in Bangladesh, the UK, and the US.

The tradeoff is voice and the kind of posts available.

• This is a commercial pitch aimed at owners — 'Comment WEBSITE or send me a DM' — and the live stores are listed as proof of shipping, not walked through.
• It shows the stores exist and that an owner can run them, but not the patient, jargon-stripping explanation a non-technical client needs in the room.
• That matters for a campaign for a Detroit small-business client: the overseas shop examples fit the store-building task, but not the local context Donovan Brown's work covers.
• Ask for evidence of local client work and in-person client explanations before choosing this for that campaign.

Examples: Source 1 · Source 2

Their matrix post reframes the binary into four quadrants by differentiation value and volume, then puts numbers on it: at $50M in annual processing, 2.9% Stripe fees run about $1.45M a year, which can justify a hybrid build.

• They price the hidden costs clients usually miss — platform lock-in (a Shopify-to-custom migration at $200K and up), technical debt from small tweaks, and constraint creep — and give a rule of thumb: buy commodity services, customise mid-tier differentiators, build core IP.
• Their other post applies the same business-case thinking to the WordPress-versus-Shopify choice.
• For an agency advising a larger client on whether to move off a platform, this is the sharper material.

The tradeoff is distance from the storefront floor.

• This work sits at the strategy and architecture level, aimed at decision-makers weighing custom builds, not merchants who need to be shown how to change a price.
• It brings clear cost logic and decision criteria, but shows no hands-on Shopify build, client session, or handover — the parts of launching a small store and leaving the owner able to run it that Donovan Brown's posts cover.
• The heavy display format also targets an engaged technical audience, unlike the plain, step-by-step client explanation needed for that launch.
• Choose it when the client's question is build-versus-buy, not when the job is to launch a small store and leave the owner able to run it.

Examples: Source 1 · Source 2