Workflow library

Every AI workflow we run for Shopify stores.

29 workflows in 9 packages, set up and run by our team. You keep every decision that matters.

Get the three packages that fit your store best, from its public pages.

29 workflows in 9 packages

Email and lifecycle

Email campaign production

Keep your email calendar full with on-brand campaigns, without a days-long brief, design and copy cycle for every send.

How it runs

What goes in

  • Your brand rules
  • Approved product information
  • A one-line campaign request

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • The angle
  • The offer
  • The send

What comes out

Klaviyo draft, ready for review

2 workflows in this package

  • What you get

    A request like “welcome email 2, feature our bestseller” becomes a brand-accurate email, checked against a fixed QA pass and saved as a Klaviyo draft.

    First step

    Confirm your brand reference and a draft-only Klaviyo key, then run one campaign from request to approved draft.

    Access

    Your storefront, your brand reference and a Klaviyo key limited to drafts.

    Limits

    • QA covers design and structure. The offer and facts are checked by your team.

    Example output

    Request to draftIllustrative example
    Request
    “Welcome email 2, feature our bestseller”
    Draft
    Subject: The one customers reorder most
    Checks
    Visual QA passed; offer left for your review
  • What you get

    Paste the link to one Figma email frame and get a native Klaviyo draft that matches it, ready for review.

    First step

    Set up a scoped Klaviyo credential and test it on one conversion before a real send.

    Access

    Read access to the Figma frame and a scoped Klaviyo credential, stored securely.

    Limits

    • Some Figma layouts don’t map cleanly to email HTML. A comparison after conversion catches them.

    Example output

    Conversion readbackIllustrative example
    Input
    Figma frame: Spring launch, email 1
    Output
    Native Klaviyo draft, six blocks
    Flagged
    Rounded image corners render square in Outlook

Email and lifecycle

Klaviyo lifecycle operations

Keep flows and lists correct, keep your Klaviyo bill in line with real engagement, and get a clear read on what moved each month.

How it runs

What goes in

  • Campaign and flow results
  • List growth and engagement
  • Deliverability signals

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • Who counts as unengaged
  • Each suppression
  • The billing tier

What comes out

Monthly review and cleanup plan

4 workflows in this package

  • What you get

    A structured report from Klaviyo that compares the month to a reference period, groups campaigns by intent, calls out top flows and digs into any KPI that moved more than expected.

    First step

    Confirm a read-only Klaviyo connection with at least one full prior month of data.

    Access

    Read-only Klaviyo access.

    Limits

    • A promotion or outage that Klaviyo can’t see shows up as an anomaly until someone adds the context.

    Example output

    Review highlightsIllustrative example
    Moved
    Welcome flow revenue, above the reference period
    Noise
    Campaign open rate, within its usual range
    Digging into
    Abandoned checkout conversion
  • What you get

    Each month, unengaged profiles are identified against a definition you approved, a dated export is archived, and suppression happens only after you approve that month’s list.

    First step

    Agree on what counts as unengaged for your store before the first run.

    Access

    Klaviyo segment, suppression and billing-usage access.

    Limits

    • A standing approval isn’t accepted. Each month’s list needs its own approval.

    Example output

    Monthly cleanup, ready for approvalIllustrative example
    Unengaged
    No opens or clicks in 180 days, as you defined it
    Before
    Dated export archived
    Waiting on
    Your approval of this month’s list
  • What you get

    Every Monday, a three-line update: anything concerning last week, and how the month is tracking. It says so plainly when there’s nothing to report.

    First step

    Name the person who acts on the update, then run one rehearsal week.

    Access

    Read-only Klaviyo access.

    Limits

    • Revenue by channel follows Klaviyo’s attribution, so it can differ from Shopify’s totals.
    • Updates go to LHG’s internal channel for your account today.

    Example output

    Monday updateIllustrative example
    Last week
    No significant anomaly detected
    This month
    Flow revenue tracking ahead of campaigns
    Action
    None needed
  • What you get

    A banner that shows only between the dates and times you set, then disappears on its own, with the original flow email untouched.

    First step

    Send the start and end times, the banner image and the flow email it belongs in.

    Access

    Edit access to that flow email in Klaviyo.

    Limits

    • Emails already delivered keep the banner, since inboxes cannot be recalled.
    • It relies on your Klaviyo account timezone being set correctly.

    Example output

    Flow bannerIllustrative example
    Banner
    Fall sale, 20% off throws
    Shows
    Oct. 3, 9 a.m. to Oct. 6, 11:59 p.m.
    After
    Removed on its own, flow unchanged

Email and lifecycle

Klaviyo strategy and audits

Know what works in your Klaviyo account, which flows to build next and how widely to send, from your own numbers.

How it runs

What goes in

  • Read-only Klaviyo access
  • Your campaign and flow history
  • Your brand and customer notes

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • The priorities
  • The flow plan
  • Any change to segments

What comes out

Findings and a flow plan, ready to review

Talk to us about this package

Scoped in a conversation, not by the store check.

4 workflows in this package

  • What you get

    One detailed review of send times, subject line fatigue, list health and flow performance, with fixes tied to your own numbers.

    First step

    Connect a read-only Klaviyo key so the review can pull your real campaign and flow data.

    Access

    Read-only Klaviyo access to campaigns, flows, lists and metrics.

    Limits

    • An on-demand review, not a recurring report. The monthly review handles ongoing tracking.

    Example output

    Account reviewIllustrative example
    Send time
    Tuesday morning sends open best
    Fatigue
    Subject lines naming the sofa are wearing out
    Status
    Six fixes ranked, waiting for your review
  • What you get

    One shareable dashboard with all three views, built from a single 90-day pull of your campaign data.

    First step

    Confirm you sent at least 10 campaigns in the last 90 days, then connect read-only Klaviyo access.

    Access

    Read-only Klaviyo access to campaign reports.

    Limits

    • It covers the three views it is built for. The full account review goes deeper.
    • It needs a steady volume of recent campaigns to say anything useful.

    Example output

    Klaviyo dashboardIllustrative example
    View 1
    Best send hour, by weekday
    View 2
    Subject line wear over 90 days
    View 3
    Emails per week, by segment
  • What you get

    An engaged-send window for each audience and market, backed by your data, showing where widening it stops paying off.

    First step

    Check that your engagement segments carry a day count in their names, such as engaged 90 days, then connect read-only access.

    Access

    Read-only Klaviyo access to campaign and audience breakdowns.

    Limits

    • It needs segment names that carry a day count. Other naming needs a quick cleanup first.
    • It recommends a window. It never edits a segment.

    Example output

    Send-depth analysisIllustrative example
    Audience
    Canada, full list
    Window
    Widen from 90 to 120 days
    Why
    Revenue per send holds to 120 days, then drops
  • What you get

    A researched plan for every relevant flow, with triggers, timing and messaging direction, shared as one page.

    First step

    Share your website and any customer personas so the research can start.

    Access

    Your public website. The finished plan is shared as a document.

    Limits

    • A plan, not the finished emails. Writing and building come next.
    • The more brand and customer detail you share, the sharper the plan.

    Example output

    Flow planIllustrative example
    Flow 1
    Welcome series, 3 emails over 7 days
    Flow 2
    Browse abandonment for sofas and chairs
    Status
    Plan ready for your review

Storefront and conversion

Conversion and landing page improvements

Find where shoppers drop off on your key pages, then fix those pages without putting what already works at risk.

How it runs

What goes in

  • Your storefront pages
  • Heatmap or PostHog data, if connected
  • Reviews and survey answers

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • The priorities
  • The page changes
  • The merge

What comes out

Ranked fixes, each with its evidence

3 workflows in this package

  • What you get

    Specific fixes for your homepage, top product pages and checkout path, each tied to something visible, like a page observation, a heatmap, a review or a survey answer.

    First step

    Run a teardown of your homepage or top product page from public data alone. No connections needed to start.

    Access

    Your public storefront. Heatmap or PostHog adds behavior data.

    Limits

    • The audit is read-only. Theme changes are a separate, reviewed piece of work.

    Example output

    Fix list, homepageIllustrative example
    Fix 1
    State the offer in the hero
    Why
    The hero names the brand but gives no reason to buy
    Ships as
    A theme branch, merged after your review
  • What you get

    A launch-ready page added to your existing theme, using your real products, prices and images. Every existing theme file stays exactly as it was.

    First step

    Confirm access to your theme repository and share one campaign brief that names the products to feature.

    Access

    Read access to your Shopify catalog and a branch of your theme repository.

    Limits

    • A vague brief makes a vague page. Name the products or collections to feature.

    Example output

    Launch pageIllustrative example
    Brief
    Autumn linen collection, six products
    Built
    New page and sections, existing files untouched
    Review
    Pull request with a live preview link
  • What you get

    An audit scored on profit per visitor across six levers, reviewing your past tests and proposing the next ones with exact price points and decision rules.

    First step

    Confirm your store already tests with Intelligems, then connect that account.

    Access

    Read-only access through your existing Intelligems connection.

    Limits

    • Only for stores that already test with Intelligems.
    • Built on an open-source profit framework, which the audit credits.

    Example output

    Profit auditIllustrative example
    Lever
    Free shipping threshold
    Test next
    Raise it from $99 to $119
    Decide by
    Profit per visitor after two weeks

Reporting and monitoring

Performance reporting and anomaly watch

Catch broken tracking or a sudden drop the week it starts, and walk into every monthly review with numbers that reconcile.

How it runs

What goes in

  • Shopify sales and orders
  • Klaviyo email results
  • Site behavior from Heatmap or PostHog

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • The reference period
  • The explanation
  • What happens next

What comes out

Verified monthly report and daily alerts

3 workflows in this package

  • What you get

    A monthly deck where totals reconcile, each KPI is compared to a sensible reference period, and outliers are investigated before the meeting.

    First step

    List which sources apply to your store, then run one full cycle before the first real review.

    Access

    Read-only access to Shopify and the other tools in scope.

    Limits

    • If a source disconnects mid-month, the reconciliation step flags the gap instead of reporting a partial total.

    Example output

    Monthly deckIllustrative example
    Reconciled
    Shopify and Klaviyo revenue totals
    Compared to
    Same month last year
    Investigated
    A spike in returns, traced to one product
  • What you get

    A daily read-only check of your Shopify and PostHog data. The LHG team gets an alert when a real anomaly appears, and nothing when there’s nothing to say.

    First step

    Confirm which data is in scope and let one week of comparable data build up.

    Access

    Read-only Shopify and PostHog data, within a scope you approve.

    Limits

    • Alerts go to the LHG team today, not directly to your team.
    • No alert fires until two comparable weeks of data exist.

    Example output

    Daily watch alertIllustrative example
    Changed
    Mobile checkout conversion dropped since Tuesday
    Checked
    Shopify orders against PostHog sessions
    Next
    Confirm whether Tuesday’s theme update touched checkout
  • What you get

    A short weekly report with charts that sets order data beside on-site behaviour, split by device, traffic source and country, with each source shown on its own.

    First step

    Confirm your analytics connections, then run a first 12-week baseline.

    Access

    Read-only Shopify orders and analytics, and read-only access to your behaviour analytics tool.

    Limits

    • Our team refreshes the data each week before the report is built. It does not update itself yet.
    • Behaviour tools capture a sample of orders, so they are read as a diagnostic, not as revenue.

    Example output

    Weekly funnelIllustrative example
    Week
    Sept. 15 to 21
    Flag
    Mobile add-to-cart down on last week
    Split
    By device, source and country

SEO and content

SEO page briefs and technical fixes

Help product and collection pages get found by fixing what holds them back and briefing pages around what shoppers search for.

How it runs

What goes in

  • Your product and collection pages
  • Structured data and titles
  • Search data, if you connect it

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • Which fixes matter
  • The brief
  • The published copy

What comes out

Technical audit and page briefs

1 workflow in this package

  • What you get

    An audit that names what’s broken, and briefs that give a writer what they need to match search intent and still read well for shoppers.

    First step

    Run one technical audit or one page brief on a real page of your store.

    Access

    Your public storefront. Search data improves keyword findings.

    Limits

    • The first audit starts on one real page, then widens to the pages that matter most.

    Example output

    Page brief, collection pageIllustrative example
    Search
    linen bedding
    Fix first
    Titles repeat the store name; no product structured data
    Draft
    Intro copy, sent for your approval

SEO and content

Blog and content program

Publish content with a plan behind it: the right topics for your readers, briefs built on evidence and drafts in your voice.

How it runs

What goes in

  • Your existing content and its results
  • Your readers and your voice
  • Your priorities and team time

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • The topics
  • Each brief
  • Each draft before it goes live

What comes out

A calendar, briefs and drafts, ready to review

Talk to us about this package

Scoped in a conversation, not by the store check.

3 workflows in this package

  • What you get

    A ranked list of what to publish, refresh or retire, turned into a calendar that fits your team’s time, with owners and review dates.

    First step

    Define who the content is for and how it should sound, from what you already know about your customers.

    Access

    Read-only access to your blog and any search or analytics data.

    Limits

    • Your reader and voice profile comes first, so the calendar follows that setup.

    Example output

    Content calendarIllustrative example
    October
    How to choose a sofa for a small room
    Refresh
    Wood care guide, facts out of date
    Owner
    Your marketing lead, review on the 15th
  • What you get

    A brief that names the reader’s problem, the main point and the evidence it will cite, then a full draft in your approved voice, ready for an editorial pass.

    First step

    Pick one approved topic from the calendar to brief first.

    Access

    The sources the brief will cite and your approved voice profile.

    Limits

    • Nothing is published without a human edit and your approval.

    Example output

    Content briefIllustrative example
    Reader
    First-time sofa buyer in a condo
    Main point
    Measure the doorway before the room
    Evidence
    Your delivery notes and return reasons
  • What you get

    A plain read of which pieces pull their weight, with refreshed versions of the ones worth saving, in their original voice.

    First step

    Connect the analytics you already use for your blog.

    Access

    Read-only access to your content analytics and the pieces to refresh.

    Limits

    • The review is only as good as the analytics connected.
    • Refreshes are proposed for review, never published directly.

    Example output

    Content reviewIllustrative example
    Keep
    Sofa size guide, still bringing readers
    Refresh
    Wood care guide, facts out of date
    Retire
    Last year’s holiday gift list

Creative and brand

Product photos, copy and French

Get product photos, page copy and Quebec French versions made at catalogue speed, with a person checking everything before it goes live.

How it runs

What goes in

  • Your product photos and titles
  • Your brand voice
  • The page or campaign brief

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • The creative direction
  • Each image before import
  • The final wording

What comes out

Images, copy and French versions, ready to review

Talk to us about this package

Scoped in a conversation, not by the store check.

3 workflows in this package

  • What you get

    A consistent set of on-model photos for each product, a hero shot, a movement shot and a detail crop, delivered as a file ready to import.

    First step

    Pick a product category and agree on a creative brief for models, backdrop and framing.

    Access

    Your reference product photos and your product import process.

    Limits

    • The product title sets the colour. A product without an accurate reference photo is flagged for a real shoot.
    • Every image passes a human quality check before use.

    Example output

    Product photosIllustrative example
    Product
    Linen robe, oat
    Shots
    Hero, movement and detail crop
    Status
    Passed quality check, ready to import
  • What you get

    New or rewritten copy for your homepage, a landing page or product pages, checked against our quality checklist before it reaches you.

    First step

    Share the page, or the brief for a new one, and your brand voice materials.

    Access

    The page content only. Your team, or ours once you approve, puts it live.

    Limits

    • Delivered as a draft for review, never published directly.

    Example output

    Homepage copyIllustrative example
    Headline
    Furniture made to be lived on
    Subhead
    Solid wood, delivered free across Quebec
    Status
    Draft, waiting for your review
  • What you get

    French versions of your emails, pages or guides that read as if they were written in French for Quebec, with the meaning kept intact.

    First step

    Share the English source and any terms you always or never use.

    Access

    No system access. A document or text handoff is enough.

    Limits

    • A language and tone pass, not a fact check of the source.
    • Suited to marketing and educational copy, not legal or regulated text.

    Example output

    French versionIllustrative example
    English
    Back in stock this week
    French
    De retour en stock cette semaine
    Note
    Wording checked for Quebec shoppers

Foundation and custom builds

AI foundation for your team

Give your team one AI workspace that knows your brand, products and policies, set up by LHG and owned by you.

How it runs

What goes in

  • Your storefront and catalog
  • Brand guides and past campaigns
  • A discovery call with your team

Lake House Group runs it

Lake House Group runs it

Set up on your store, checked by our team

You approve

  • What goes in
  • Who gets access
  • The handover

What comes out

A workspace you own

Talk to us about this package

Scoped in a conversation, not by the store check.

2 workflows in this package

  • What you get

    A workspace with your brand knowledge, product and policy data and training material, run by LHG and owned by you.

    First step

    Gather what LHG already knows about your brand and schedule a discovery call with your founder.

    Access

    The materials you choose to share. Write access only to your own workspace.

    Limits

    • Nothing moves into your workspace until you authorize it.

    Example output

    Workspace contentsIllustrative example
    Brand
    Voice guide, colours, logos
    Products
    Catalog, sizing and policies
    Gap
    Return policy wording not found in your sources
  • What you get

    One brand reference with design tokens, logos, a voice guide and a product image library. Anything your sources don’t answer is marked as a gap.

    First step

    Share your storefront and whatever brand material you have. The first output shows what was found and what’s missing.

    Access

    Your storefront, Shopify catalog, Figma if you use it, and a few sent emails.

    Limits

    • When your brand guide and your live site disagree, both are recorded and the conflict is flagged.

    Example output

    Brand referenceIllustrative example
    Found
    Colours, fonts and logo files from your site and Figma
    Voice
    Built from your last twenty sent emails
    Conflict
    Guide says navy, site uses black; both recorded

Builds and custom work

Work that stands on its own, scoped one project at a time.

Tell us what you want built

Each project starts with a short call and a written scope you approve before any work begins.

4 services, each scoped on its own

  • What you get

    Each request becomes a locked scope with acceptance criteria, built on an isolated branch, previewed, and merged only after your sign-off.

    First step

    Turn your first feature request into a scoped task plan.

    Access

    Branch access to your theme repository and a preview environment.

    Limits

    • New asks during a build become a new task.

    Example output

    Scoped taskIllustrative example
    Request
    Add a size guide to product pages
    Done when
    Opens from the size selector on mobile and desktop
    Ships
    After your sign-off on the preview
  • What you get

    A scoped build that solves one specific problem, tested against real data and handed over with documentation.

    First step

    Describe the need. We check that no existing package covers it, then write a short spec.

    Access

    Only what the specific build needs, for as long as it needs it.

    Limits

    • Scoped one project at a time.

    Example output

    Short specIllustrative example
    Need
    A quiz that suggests a bedding size
    Checked
    No existing package covers it
    Handover
    Tested on real catalog data, with documentation
  • What you get

    A branded training guide in English and Quebec French, as a private web page and a PDF, built from your own returns, shipping and loyalty rules.

    First step

    A short interview to confirm your POS, your loyalty program and any pre-order setup.

    Access

    Your live policy pages, to confirm the real terms.

    Limits

    • Built for each store, not a subscription.
    • Anything you cannot confirm stays marked as open instead of guessed.

    Example output

    Training guideIllustrative example
    Section
    Returns at the register
    Rule
    30 days, with a receipt or order number
    Format
    Private web page and PDF, EN and FR
  • What you get

    A shortlist of programs your project likely fits, and a drafted application ready for your review and submission.

    First step

    Tell us about the project, your sector and a rough budget so we can match programs.

    Access

    No system access. You share project and company details directly.

    Limits

    • A match is not funding. Each program decides, and you or your accountant submit the application.
    • Complex tax credits such as SR&ED go to a specialist.

    Example output

    Grant shortlistIllustrative example
    Program
    A digital adoption program for small businesses
    Fit
    Project and budget match the criteria
    Status
    Draft application ready for your review

Store scan

See which three fit your store.

Enter your store’s address. We read its public pages and rank the packages that fit, with the evidence behind each. No email, no login.

No email, no login. Just your store’s address.

What matters most right now?

If the scan finds a matching package, this can move it earlier in your plan.

Competitor stores, up to two

We compare public product-page signals from these stores. The comparison does not change your ranking.