Role Automation Blueprint Intake

Your answers save automatically as a draft in this browser (on this device only, tied to this order) and the draft is cleared once you submit.

How we handle your answers. Your answers go only to the Northfold team preparing your blueprint. They are used to build your delivery, encrypted in transit where HTTPS is deployed, deleted from the relay once we have received them, and never published or sold. Intake links expire and full technical details are on our privacy page.

Do not paste secrets. We never need passwords, API keys, customer records, or payroll data. Describing the work is enough. This form does not upload files; if a file would help, we will ask for it by email.

Contact

About you (buyer)

Buying this for someone on your team? The best blueprints come from the person who actually does the work. Have them fill this in, or sit with them while you do.

Role basics

Responsibilities

List the main things your role is responsible for. A few words each is fine, so we know what the work actually is. At least one is required.

Tools

The software and tools you use in this role. Tick the common ones, add anything else under Other tools, and use the detailed rows below for tools where frequency or your access level matters. At least one tool is required.

Add a detailed row for any tool where it matters how often you use it or what access you have.

Workflow examples

Describe real workflows you run. Concrete beats polished. At least two complete workflows are required. Include the trigger, tools, time burden, data sensitivity, judgment, and whether it sends, updates, or deletes anything. Those last questions are what keep the recommendations safe to act on.

Judgment required: how much thinking a step needs:

Low: the rules or a checklist make the answer clear; almost anyone could do it the same way.
Medium: routine, but sometimes it needs a call or a judgment.
High: it needs experience, taste, or authority, and getting the call wrong has real consequences.

Data sensitivity: how confidential the information involved is. If you are unsure, choose the higher level.

None: public or harmless information.
Low: internal, but low-risk if seen.
Medium: business-confidential information, such as client lists, pricing, pipeline, or internal reports.
High: regulated, personal, financial, legal, credential, payroll, or health data, or anything highly confidential.

Worked example of a useful workflow answer

Name: Weekly new-client onboarding
Trigger: Signed contract lands in the shared inbox
Steps: Create the client folder, copy the onboarding checklist, set up their CRM record, send the welcome email, and schedule the kickoff call.
Tools: Gmail, Google Drive, HubSpot
Time each time: About 1.5 hours
Judgment: Medium. Mostly a checklist, but I decide kickoff timing and flag anything unusual in the contract.
Data sensitivity: Medium. The contract and CRM record are business confidential.
Sends outside the company?: Yes. The welcome email goes to the client.
Updates records?: Yes. It creates the client's CRM record.
Deletes records?: No.
Notes / exception: If the contract has non-standard terms, I stop and ask the account lead before sending anything. The welcome email must never go out before the CRM record exists.

Pain points

Data and document access

Approvals and compliance

This helps us design automation that stays inside your guardrails. Please answer the first question. "No one" and "not sure" are useful answers, not blanks.

Goals

AI literacy

There are no wrong answers here. This just helps us tailor the setup guidance to your comfort level and to what your workplace allows. Beginners and experts both get a blueprint that fits.

Optional uploads (metadata only)

Describe files you could share later, such as SOPs, exports, or screenshots. This form does not upload the files themselves. Filename, kind, and description only.

Consent

Leaving this unchecked allows de-identified workflow, tool, and friction patterns to improve the recommendation library. Your identity, employer name, and private intake answers are never published or sold either way.

Tell us how the work actually gets done.

Role Automation Blueprint intake

Before you start

Contact

About you (buyer)

Role basics

Responsibilities

Tools

Email & calendar

Docs & storage

Communication

CRM & sales

Projects & tasks

Finance & operations

Automation & AI

Workflow examples

Worked example of a useful workflow answer

Pain points

Data and document access

Approvals and compliance

Goals

AI literacy

Optional uploads (metadata only)

Consent