Skip to content

Pack · Software development agency

Project-based dev agency pack

A project-based dev agency sells fixed or capped builds out of a paid discovery phase, so it always needs the next project.

Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.

Workflows
4
Steps
27
Client fills in
11
Starts
From a form, Calendly or Pipedrive, within seconds, or at a set time

The workflows in this pack

Built for software development agencies.

  1. 01

    Lead rescue for software development agencies

    Answer every new lead within a minute, get the owner on the emergencies, and chase anyone nobody has called back within the hour.

    1. Starts whenA form is sent
    2. TextInstant reply
    3. EmailEmail acknowledgement
    4. Web requestSend to CRM or sheet
    5. BranchEmergency?
    6. IfIf urgent
    7. TextText the owner now
    8. Wait · 10 minGive the owner 10 minutes
    9. BranchOwner acknowledged?
    10. IfIf not yet
    11. TextEscalate
    12. IfIf acknowledged
    13. IfIf otherwise
    14. Wait · 1 hourWait an hour
    15. BranchHas anyone contacted them?
    16. IfIf not yet
    17. TextThe rescue
    18. NotifyTell the owner
    19. IfIf contacted
  2. 02

    Booking brief for software development agencies

    When someone books, send the owner a four-line brief: who they are, what they want, what they said, and one question worth asking.

    1. Starts whenSomeone books a meeting
    2. AgentWrite the brief
    3. NotifyTell the owner
  3. 03

    Quote follow-up for software development agencies

    Nudge every unanswered quote two, five and ten days after it was sent, and tell the owner which are going stale.

    1. Starts whenOn a schedule
    2. Airtable: Find recordsQuotes sent two days ago
    3. For eachEach one
    4. TextCheck they got it
    5. Airtable: Find recordsQuotes sent five days ago
    6. For eachEach one
    7. EmailOffer to talk it through
    8. Airtable: Find recordsQuotes sent ten days ago
    9. For eachEach one
    10. TextLast nudge
    11. NotifyTell the owner
  4. 04

    Won-deal kickoff for software development agencies

    When a deal is won, open the kickoff task, tell the team, and hand the owner the welcome to send, the same minute.

    1. Starts whenA deal is won
    2. App stepKick off the deal
    3. App stepTell the team
    4. NotifyTell the owner

What each client fills in

Business name
How the texts and emails sign off.
Owner’s mobile
Rung for emergencies. Add a second number after a comma and the escalation goes there.
Owner’s email
Gets one line for every lead the workflow rescues.
Booking or quote link
Sent to a lead nobody has contacted after an hour.
AI model
The model the client’s key can use.
Airtable base ID
The base that holds the records this sweeps.
Airtable table
The table it reads each day.
Task list ID
The ClickUp list new-client tasks go into.
First steps
What the kickoff task says to do: the call, the access to collect, the first deliverable.
Team channel
The Slack channel that hears about it.
Welcome message
The welcome the client gets, kept to send by hand while the deal record has no contact email.

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

  • Webhook URL (CRM or sheet)

  • Calendly

    In the client’s Calendly: Integrations & apps → API and webhooks → Personal access tokens → Generate new token, with the scopes scheduling_links:write (booking links) and, for the triggers, users:read, webhooks:read and webhooks:write. A token made before Calendly introduced scopes keeps full access.

  • platform.claude.com → Settings → API keys → Create key, in the workspace that bills this client.

  • Airtable

    airtable.com/create/tokens → Create token → scopes data.records:write and data.records:read (lookups and the triggers) → add the client’s base → copy the token.

  • In the client’s Pipedrive: your avatar → Personal preferences → API → copy the token.

  • In the client’s ClickUp: avatar → Settings → Apps → API Token → Generate.

  • In the client’s Slack: api.slack.com/apps → Create New App → OAuth & Permissions → add the chat:write scope (and channels:history, plus groups:history for a private channel, for the message trigger) → Install to Workspace → copy the Bot User OAuth Token. Invite the app to the channel.

After you install it

It lands switched off. The client’s checklist holds exactly this:

  1. Pick the client’s form that starts it
  2. Connect the client’s Twilio (SMS), for “Instant reply”, “Text the owner now”, “Escalate” and “The rescue”
  3. Connect the client’s Resend (email), for “Email acknowledgement” and “Tell the owner”
  4. Connect the client’s Webhook URL (CRM or sheet) (optional: the step can be turned off instead), for “Send to CRM or sheet”
  5. Fill in Business name (How the texts and emails sign off)
  6. Fill in Owner’s mobile (Rung for emergencies. Add a second number after a comma and the escalation goes there)
  7. Fill in Booking or quote link (Sent to a lead nobody has contacted after an hour)
  8. Fill in Owner’s email (Gets one line for every lead the workflow rescues)
  9. Connect the client’s Calendly, for “Someone books a meeting”
  10. Connect the client’s Anthropic, for “Write the brief”
  11. Connect the client’s Resend (email), for “Tell the owner”
  12. Fill in AI model (The model the client’s key can use)
  13. Fill in Business name (How messages sign off)
  14. Fill in Owner’s email (Gets the summaries and the cases a person must handle)
  15. Confirm with the client: The client’s Calendly is on a paid plan (Standard, Teams or Enterprise): Calendly sends webhook events only on those.
  16. Connect the client’s Airtable, for “Quotes sent two days ago”, “Quotes sent five days ago” and “Quotes sent ten days ago”
  17. Connect the client’s Twilio (SMS), for “Check they got it” and “Last nudge”
  18. Connect the client’s Resend (email), for “Offer to talk it through” and “Tell the owner”
  19. Fill in Airtable base ID (The base that holds the records this sweeps)
  20. Fill in Airtable table (The table it reads each day)
  21. Fill in Booking link (Where a customer picks a time)
  22. Connect the client’s Pipedrive, for “A deal is won”
  23. Connect the client’s ClickUp, for “Kick off the deal”
  24. Connect the client’s Slack, for “Tell the team”
  25. Fill in Task list ID (The ClickUp list new-client tasks go into)
  26. Fill in First steps (What the kickoff task says to do: the call, the access to collect, the first deliverable)
  27. Fill in Team channel (The Slack channel that hears about it)
  28. Fill in Welcome message (The welcome the client gets, kept to send by hand while the deal record has no contact email)

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.