Visible boundaries for what gets quoted, escalated, or declined.
The public scope is meant to be operational, not aspirational. It defines the lanes that
fit the fixed-scope offer, the categories that are declined outright, and the deterministic
routing outcomes used during intake review.
The primary fit is a bounded internal workflow build for an SMB operator. These lanes are
the only categories the public offer is designed around.
Internal operations: Workflow automation for internal business processes and team operations.
Support: Internal support and service workflows with named human review boundaries.
Content workflows: Content preparation, drafting, and operations support without broad publishing automation claims.
Founder tooling: Small-team workflow tooling that stays inside the narrow productized delivery model.
How routing works
Intake submissions are reviewed against a fixed rubric. The possible outcomes are visible
in advance so prospects can see whether the request belongs in the default lane, needs
escalation, or should not proceed.
Decline: Any closed disqualifier or Annex III creep guard is triggered.
Tier 2: The request stays within the internal ops, support, content, or founder-tooling lane and fits the primary fixed-scope offer.
Tier 3 with legal review: The request is otherwise viable but needs a higher-complexity documentation pack or separate legal/compliance review before quoting.
These categories are outside the offer and are not quoted through the public intake flow.
Hiring: Requests involving hiring or candidate decision workflows are declined.
Credit or scoring: Requests involving credit, scoring, or trade-credit decisioning are declined.
Biometrics: Requests involving biometric identification, categorization, or related systems are declined.
Law enforcement: Requests involving law-enforcement use cases are declined.
Migration: Requests involving migration control or border-management decisioning are declined.
Public authority: Requests for public-authority decision systems are declined.
Annex III creep guards
Higher-risk extensions that still get declined
Even when a workflow looks operational on the surface, it is declined if it drifts into
these decision-influencing patterns.
Employment decision influence: Decline outputs influencing employment, performance, retention, or compensation decisions about workers, contractors, or candidates.
Access or refund gating: Decline outputs gating user access, refunds, or account status without a human reviewer.
Credit or payment-term classification: Decline outputs classifying customers, leads, or counterparties for credit, payment terms, or trade-credit.
DSA-platform moderation pipelines: Decline moderation or labeling pipelines for end-user content where the client is a DSA platform.
What legal review means here
A Tier 3 outcome is not an approval and not a compliance certification. It means the
request may be viable only if the workflow can be framed with additional documentation,
explicit boundaries, and separate legal or compliance review before quoting.
What this page does not claim
This page explains fit and decline logic. It does not promise legal coverage, does not
state that a workflow is AI Act compliant, and does not replace the client's own review
obligations.