Beginner's question: What exactly counts as a 'task' versus an 'activity'?

Ran LogicGate in a 1,200-person financial services shop for three years. Handled vendor risk, SOC2 audits, and access certifications.

**Task**: A single assignable unit of work for one person. In vendor onboarding, "Complete security questionnaire" is a task. Pricing typically runs $2-5 per task per month in my experience.
**Activity**: A collection of tasks that form one logical step. "Initial vendor screening" is an activity containing tasks like "Check sanctions list" and "Collect business justification." Activities are the higher-level cost bucket, often 2-3x the task price.
**Cost multiplier**: The real trap is automated tasks. If you auto-generate 10 "review" tasks for every new vendor via an API call, that's 10 billable tasks, not one activity. Watch your integrations.
**Where it breaks**: The model gets murky with parallel approvals. Four people approving one contract is four tasks, but feels like one activity. Your bill disagrees.

If you're building simple, linear workflows with few users, focus on the activity count. If you're automating anything with bulk assignments, model task volume first.

Tell me your expected concurrent vendors per month and if you'll hook it to your HR system, and I'll tell you which metric will bite you.

Your point about parallel approvals is the key to budgeting for this. The platform doesn't care about logical grouping, it just counts tasks. That "four people, one contract" scenario is a classic budget killer, especially if you're running it for hundreds of vendors.

The other hidden cost is task churn. If someone rejects a questionnaire and sends it back for revision, that's often a new, billable task instance created, not a continuation of the old one. Your monthly task count isn't just new work, it's all the rework.

That "in simple terms" request is the first red flag. The simple explanation is the marketing one, which intentionally blurs the lines to make the pricing seem less scary than it is.

User911's breakdown is technically correct, but it misses the strategic fudge factor. LogicGate's own documentation gets vague on the edges. Is a five-question form one task or five? If you have a conditional branch where *either* Task A *or* Task B fires, is that counted as one potential task or two for pricing? The platform often counts for the maximum possible, not the probable path.

For your vendor onboarding example, the real cost isn't in defining "collect insurance certificates" as a task. It's in all the invisible, system-generated tasks your process will inevitably spawn: the approval requests, the follow-up reminders, the notification tasks for stakeholders who just need to be informed. Those are all billable tasks. You don't build them, but the platform creates them, and you pay for them.

So you're not just budgeting for the workflow you design. You're budgeting for the administrative overhead the platform injects into it.

Yeah, that parallel approval trap is brutal. It reminds me of a K8s HorizontalPodAutoscaler generating way more pods than you budgeted for because you didn't account for a sudden burst. The system just sees "four tasks created" and bills you, even though the human sees it as "one step."

Your point about task churn is super valid. It's not just rework, either. Think about automatic escalations or reminders. If the system auto-generates a "follow-up" task after 7 days of inactivity, that's another billable unit. Your monthly volume becomes a function of your team's *inaction*, which is a tough cost to predict.

The budgeting lesson here is to model your process in the worst-case, not the happy path. Count every possible branch and parallelization as a separate task. It's the only way to avoid surprise bills. 😅