Question 1

How long does setup take with Make vs. Zapier?

Accepted Answer

With Make, expect about 20–30 minutes from purchase to live — import the blueprint, connect your email tool, paste in your copy, and you are receiving new sign-ups into the sequence. With Zapier, the same flow takes a bit longer because Zapier steps are one-action-per-Zap, so the four-emails-and-segments layout ships as a paired instruction set; most teams finish in 45–60 minutes.

Question 2

Does the sequence work with Mailchimp, ConvertKit, and Klaviyo?

Accepted Answer

Yes. The setup guide walks through each platform with the exact lists, tags, and trigger configuration you need. Mailchimp uses tags + date-based autoresponders, ConvertKit uses sequences + visual automations, and Klaviyo uses flows + the subscribed-to-list trigger. The copy files drop into any of the three unchanged.

Question 3

Can I personalize the copy with subscriber tokens?

Accepted Answer

Yes. The copy files include merge tokens for first name, business name, customer name, and lead magnet URL, with platform-specific syntax for each provider. The setup guide shows the exact field mapping per platform, and the blueprint is fully editable if you want to add or rename tokens.

Question 4

What happens if a subscriber unsubscribes mid-sequence?

Accepted Answer

Once a subscriber hits the unsubscribe link in any of the four emails, all major email platforms stop the remaining sequence automatically — no further emails go out, and the Make or Zapier trigger no longer fires for that contact. The blueprint does not need a custom off-ramp; platform-level unsubscribe handles it.

Question 5

What changes if I update the lead magnet URL later?

Accepted Answer

You change the URL in one place: the email copy file for the day-1 lead-magnet email, plus the matching token reference in the Make or Zapier blueprint. There is no database migration and no need to re-import the blueprint — most teams update the link and the next send picks it up.

Question 6

How are DocuSign envelopes addressed?

Accepted Answer

The blueprint reads the client name and email from your trigger source (CRM, spreadsheet, or form), then sends the DocuSign API a personalised envelope with the recipient role pre-mapped and the sign-here tabs positioned from your template. You keep authoring the contract in DocuSign — Make just fills in the recipient details and routes it on the right schedule.

Question 7

Where do Typeform responses land before the contract is signed?

Accepted Answer

Every intake submission is written to a Notion "Pending clients" database the moment Typeform fires, with all form fields mapped to Notion properties and the Status set to "Awaiting signature". The same row is updated to "Signed" the moment DocuSign reports a completed envelope — so the pipeline has a single, searchable record per client at every stage.

Question 8

How is Slack notification routing split between sales and ops?

Accepted Answer

The blueprint watches a tag on the trigger record: when Status = "Awaiting signature" or "Signed", ops gets the ping in #client-onboarding; when Status = "New lead" or "Welcome sent", sales gets the ping in #sales-pipeline. Tags are configurable, so teams that prefer one shared channel can route everything there instead.

Question 9

Can I customize the welcome Notion workspace for each client?

Accepted Answer

Yes. The blueprint clones a Notion template page per new client, populating client name, project name, start date, and your standard sub-pages (Brief, Files, Decisions). The template page is fully editable in Notion — add or rename sub-pages, change defaults, swap database schemas — and the cloned workspace inherits whatever you have set when the scenario runs.

Question 10

Does the flow reset if a client re-signs or comes back later?

Accepted Answer

No — the blueprint deduplicates by email. If the same client email appears in the trigger source a second time, the existing Notion row is updated (Status reset to "New lead") and the contract link is re-sent, rather than creating a duplicate Notion record or sending a fresh welcome to a client who already onboarded.

Question 11

How reliable is the Stripe webhook for stopping the sequence?

Accepted Answer

The blueprint watches Stripe for the invoice.paid event (and the equivalent status update in FreshBooks, Wave, QuickBooks, or HoneyBook). Stripe webhooks are highly reliable in practice, and Make retries failed webhook calls automatically. The scenario also re-checks payment status before each of the three follow-ups, so even a delayed webhook cannot cause a duplicate send.

Question 12

What is the tone of each of the three reminder emails?

Accepted Answer

Day 3 is a warm, low-pressure nudge — assumes the client simply overlooked the invoice. Day 7 is firm and direct, with clear payment instructions and a direct invoice link. Day 14 is the final notice — outlines next steps and signals consequences without hostility. All three copy files are fully editable, so you can adjust tone or reword per your client relationship.

Question 13

What happens after the day-14 final notice?

Accepted Answer

The final-notice email closes the sequence — no further automatic sends go out. You decide whether to take the next step manually (late-fee invoice, collections partner, write-off). The blueprint writes a "Final notice sent" marker on the invoice row so your records show the sequence ran to completion, and you can build a downstream handoff in Make if you want a Slack ping or a CRM update at that point.

Question 14

Does the sequence handle multi-currency invoices?

Accepted Answer

Yes. The blueprint reads the invoice amount and currency directly from your invoicing source and passes them into the email body as the original values — a 1,200 EUR invoice stays EUR through all three reminders. The day-7 follow-up includes the original currency code in the payment instructions so the client never has to guess at conversion.

Question 15

What happens if the client makes a partial payment?

Accepted Answer

A partial payment does not stop the sequence on its own — the remaining balance is still overdue. The blueprint includes an optional branch you can enable that swaps the day-7 copy to a "balance remaining" version once a partial payment is detected, so the reminder references the correct outstanding amount. Disable the branch and the standard day-7 reminder fires as written.

Question 16

How do Typeform fields map into the Notion CRM database?

Accepted Answer

The blueprint reads your form payload, normalizes the field names, and writes them to matching Notion properties on the included database template. Name → Name, Email → Email, the UTM or referring-page field → Source, and a computed property → Follow-up Date. Field names are configurable in one place, so you can rename form fields or Notion properties without rebuilding the scenario.

Question 17

How are Slack notifications routed between channels?

Accepted Answer

The blueprint reads a routing rule from your trigger source — by default, leads from the "Contact" form go to #sales-inbox and leads from the "Demo request" form go to #demo-queue. Rules are configurable per form field, and you can route by UTM source, lead score, or any custom tag your form supports. Channels are listed in the setup guide.

Question 18

What happens if the same lead submits twice?

Accepted Answer

The blueprint deduplicates by email address — if a second submission arrives for an email that already exists in the Notion CRM, the existing row is updated in place (latest submission overwrites Name, Source, Follow-up Date), the Status is bumped back to "New", and Slack gets a "duplicate update" ping. No new row is created and no follow-up date is silently lost.

Question 19

Can I export the Notion CRM to CSV?

Accepted Answer

Yes. Notion itself supports CSV export of any database — open the CRM database, click ••• → Export → CSV. For automated exports, the blueprint can be extended with a Make scheduler that drops a weekly CSV into Google Drive or emails it to a manager, but the base template ships without that step to keep setup minimal.

Question 20

Can I add a custom status pipeline (Qualified, Won, Lost)?

Accepted Answer

Yes. The included Notion database template uses a single Status select field, and you can rename or extend the options in Notion without touching the blueprint. If you want automated status transitions (e.g. auto-flip to "Won" when a Stripe payment lands), the setup guide shows where to add a Make branch — most teams add it in under ten minutes.

Question 21

What does the Notion content calendar schema look like?

Accepted Answer

The included Notion template has four databases: Topics (your backlog of post ideas), Drafts (in-progress posts with title, body, hashtags, image, channel), Schedule (the queued posts with date, time, and channel), and History (every published post with engagement stats from Buffer). Status fields drive the whole flow — Draft → Scheduled → Published — and Make watches those status transitions to trigger the right step.

Question 22

How does Buffer order posts in the queue?

Accepted Answer

The blueprint writes posts to Buffer in chronological order based on the Schedule database’s Date property, and Buffer then publishes each at the time you set per channel. The Make scenario respects that order — newer scheduled posts always go to the back of the queue, never the front. You can re-order manually in Buffer at any time without re-running the scenario.

Question 23

How does the per-channel approval flow via Slack reactions work?

Accepted Answer

When a draft is ready for review, Make posts it to your team Slack channel with the draft body, image, and target channels. Teammens react with ✅ to approve or ❌ to send back. Once the reaction count crosses the approval threshold you set (default: 2 ✅), Make moves the post to Schedule and pushes it into Buffer. No approval threshold met, no schedule.

Question 24

What happens when a scheduled slot has no draft?

Accepted Answer

Buffer simply skips the empty slot — nothing goes out, and Make does not invent filler content. If you want empty-slot protection, enable the optional branch in the blueprint that posts a Slack reminder to your team 24 hours before any slot with no scheduled draft, so you can fill it or accept the gap.

Question 25

How are timezones handled for scheduled posts?

Accepted Answer

Each Schedule entry stores the publish time as a Notion date with a timezone, and Make converts that to the correct UTC timestamp before pushing to Buffer. Buffer then publishes against the schedule in each channel’s configured timezone. If your team spans multiple timezones, set the channel timezone in Buffer to the audience timezone, not the author timezone — the blueprint uses the Notion-stored time as the source of truth.

Question 26

Is this Slack-native only, or does it use Make + Slack?

Accepted Answer

It runs in Make (the automation platform) and reads from / writes to your Slack workspace. Stand-ups are collected by a Make webhook that Slack workflow or the team form hits when someone submits, and every step from there — the pinned topic, the morning aggregate, the nudge, the Friday recap — is a Make module that posts back to Slack. The blueprint is fully editable inside Make if you want to add more steps.

Question 27

How do I customize the Friday recap format?

Accepted Answer

The recap template ships as a Slack Block Kit layout plus a matching HTML email layout, both pre-populated with the weekly aggregate fields (per-author Yesterday, Today, Blockers, and engagement stats). Edit the Slack blocks directly in the Make module to change layout, add a header image, or split the recap into sections — no code needed.

Question 28

What happens when a teammate is on PTO?

Accepted Answer

Two options, both supported by the blueprint: (1) the nudge module skips anyone whose Slack status is set to "PTO" or whose Notion PTO calendar shows them out, or (2) the aggregator filters out PTO teammates from the recap entirely. The default behavior skips the nudge (no annoying pings) but keeps them in the recap with a PTO marker. Switch per your team’s preference in one Make toggle.

Question 29

Can this run across multiple Slack channels (per-team standups)?

Accepted Answer

Yes. The blueprint accepts a per-channel configuration — each team’s #standup channel gets its own aggregator state, nudge schedule, and Friday recap. The setup guide shows how to clone the Make scenario per channel, or use a router module that dispatches to the right aggregator based on which channel fired the webhook.

Question 30

Can I switch the recap to a different weekday?

Accepted Answer

Yes. The Friday recap is just a scheduled aggregator + post pair, so changing the recap day is a matter of moving the trigger schedule in Make from Friday to your preferred day. The aggregator pass is day-agnostic — it always rolls up the past 5 working days from when it fires — so the recap content stays correct regardless of the day it lands.

Question 31

Do I need Notion + Make to use this template?

Accepted Answer

Yes. The blueprint runs entirely inside Make and reads from / writes to two Notion databases (one for Meeting Notes and one for the Wiki). If you don’t already use Make, the free tier covers a small team — once you cross Make’s operation threshold the scenario throttles and Make Pro (billed to Make, not to Purrly) is required.

Question 32

How long does setup take?

Accepted Answer

About 30–45 minutes from purchase to live for a small team. The flow is: complete checkout, receive the blueprint JSON by email (instant), create or import the two Notion databases (Meeting Notes + Wiki), import the JSON into Make, connect your Notion workspace, and flip the scenario on. The first publish walks you through every step in the included setup guide.

Question 33

Can I customize the wiki database?

Accepted Answer

Yes. The blueprint is fully editable — add or rename Notion fields, change the block structure, swap the email body, or wire the wiki to a different Notion view. The included setup guide shows where each block in the scenario maps to a field or block in Notion, so most edits take a few minutes.

Question 34

How do updates work?

Accepted Answer

Updates are included at no extra cost. When a template you own is updated — typically because a Notion API change ships or we improve the block layout — we send a notification email with the new blueprint JSON. The license permits modification, so you can also keep your own variant forever.

Question 35

What about Slack notifications?

Accepted Answer

The current template fires email notifications only — keep it on the same domain with the existing Slack-native Daily Stand-up Collector to cover both wiki-driven and stand-up-driven alerts. A Slack-notify module is a small edit you can add to the blueprint yourself.

Question 36

Do I need Notion + Make to use this template?

Accepted Answer

Yes. The blueprint runs entirely inside Make and reads from / writes to two Notion databases (one for Project Briefs and one for the Status Board). If you don’t already use Make, the free tier covers a small team — once you cross Make’s operation threshold the scenario throttles and Make Pro (billed to Make, not to Purrly) is required.

Question 37

How long does setup take?

Accepted Answer

About 30–45 minutes from purchase to live for a small team. The flow is: complete checkout, receive the blueprint JSON by email (instant), create or import the two Notion databases (Project Briefs + Status Board), import the JSON into Make, connect your Notion workspace, and flip the scenario on. The first board row walks you through every step in the included setup guide.

Question 38

Can I customize the status board blocks?

Accepted Answer

Yes. The blueprint is fully editable — add or rename Notion fields, change the block structure, swap Risks callouts for child pages, or wire the status board to a different Notion view. The included setup guide shows where each block in the scenario maps to a field or block in Notion, so most edits take a few minutes.

Question 39

How do updates work?

Accepted Answer

Updates are included at no extra cost. When a template you own is updated — typically because a Notion API change ships or we improve the block layout — we send a notification email with the new blueprint JSON. The license permits modification, so you can also keep your own variant forever.

Question 40

What about Slack notifications?

Accepted Answer

The current template fires email notifications only — keep it on the same domain with the existing Slack-native Daily Stand-up Collector to cover both status-driven and stand-up-driven alerts. A Slack-notify module is a small edit you can add to the blueprint yourself.

Question 41

How does the scenario handle timezones when the cron fires?

Accepted Answer

The Make scheduler fires on UTC by default, so the cron expression `0 9 * * 1` posts at 9:00 AM UTC every Monday. If your team sits in a different timezone, edit the cron expression in the Make scheduler module to fire at the equivalent UTC offset — for example, `0 14 * * 1` covers 9:00 AM Eastern during standard time. The blueprint ships with sensible defaults and a README note in the setup guide explaining the timezone math. Notably, Make also lets you bind the scheduler to a named timezone Make recognizes, so you can program 9:00 AM "your local time" without hand-converting offsets.

Question 42

Can I mix and match the data sources — Stripe + Notion + Google Sheets?

Accepted Answer

Yes. The blueprint ships with two pre-wired pulls (Stripe charges for revenue + paid counts, and Notion database query for new leads), and the aggregator step is modular — you can swap the Notion module for a Google Sheets query, a HubSpot contacts list filter, or any other HTTP module Make supports. The aggregator row YAML carries only the three final fields the Slack message reads, so every upstream swap still produces the same Monday-morning summary. The setup guide walks through the swap with a concrete example for teams that keep their lead source in a Google Sheet instead of Notion.

Question 43

What does the Slack message actually look like?

Accepted Answer

The Slack module posts a Markdown-formatted message with an emoji-headed summary: `📊 Weekly Metrics — week of YYYY-MM-DD` followed by `💰 Revenue: $X,XXX.XX`, `🧾 Invoices paid: N`, and `📥 New leads: N`, then a small signature line. The numeric formats are explicit — revenue reads in major units (divided by 100 with rounding), the week_start label is the Monday of the reporting window, and the currency code follows the operator’s Stripe default. You can edit the layout, add more fields (e.g. failed charges, refund totals), or split the message into multiple blocks — the Slack module is fully editable in Make.

Question 44

What happens if Slack rate-limits or returns an error?

Accepted Answer

Make retries transient errors automatically up to three times in a single scenario cycle, and the post is idempotent — even if the same week is re-run the message is posted again only at your discretion. If your #metrics channel ever hits Slack’s per-second message rate limit (very unlikely for one Monday morning post), Make backs off and the slack module re-tries on the next minute; no aggregation drift, no missing week. The setup guide includes a toggle for thread mode — turn it on and each subsequent post in the same week replies into the original thread instead of producing a fresh headline message.

Question 45

Can I split the metrics into one channel per team or product line?

Accepted Answer

Yes. The Slack module takes a per-channel configuration — Wire a router in Make and split the aggregator row over as many configured channels as you have teams or product lines (e.g. `#growth-metrics`, `#finance-metrics`, `#product-metrics`). The setup guide includes a drop-in router module template, and the aggregator row already carries everything each downstream channel needs; you only duplicate the Slack module per channel and pick the destination. Teams that want a single cross-organization channel keep the default and post the same payload everywhere.

Every FAQ — in one place

Welcome + Follow-Up Email Sequence

Client Onboarding Flow

Invoice Follow-up Sequence

Lead Capture → CRM

Social Media Automation

Daily Stand-up Collector

Meeting Notes → Wiki Publisher

Project Brief → Status Board

Weekly Metrics → Slack Notification

Browse every template side by side