The scoper — deterministic ruleset
The workflow scoper
Six guided questions about one repetitive process. In return you get a genuinely useful project brief: the task map, the assumptions, what the fixed scope doesn't cover, an acceptance-criteria skeleton, and an indicative classification — fits the one-workflow offer, needs a discovery workshop, or out of scope, with the human path. Keep it, download it, or send it to us for a fit review. It's never a binding quote.
Scope your workflow in six questions
Describe one repetitive process: what starts it, where the work starts and
ends, what it produces, who approves, and how often it runs. The scoper
runs on a fixed, versioned set of rules (tradeloom-scoper-v1,
shown on your brief) — a deterministic template, not an AI
system. You get a task map, a project brief you can download or
save in this browser, an explicit list of anything unsupported, and an
indicative scope classification. The brief is never a binding
quote, and sending it does not reserve time.
Your project brief
Task map
Brief (document of record)
“Save in this browser” stores your answers and brief in this browser's local storage only — no account, nothing sent anywhere. “Send this brief” copies the brief into the inquiry form below so you can review it — nothing is submitted until you complete the form and press “Send request” yourself.
Saved answers were found in this browser.
The same rules, without the scoper (static equivalent)
| Your situation | Classification | What it means |
|---|---|---|
| One clear trigger, two listed systems, an internal or staff-facing result, a few runs a day at most. | Indicative fit: One Workflow, Properly Implemented | Indicative fit for the fixed scope — still confirmed in writing after a fit review. |
| A customer/partner message or a payment that a person approves before it goes out. | Indicative fit: One Workflow, Properly Implemented | Fits, with the approval gate built in. The gate is mandatory, not optional. |
| A payment or outward message that should run with no approval step at all. | Out of scope as described | Never built. High-impact external actions require a human approval step. |
| A system outside the supported list, high/continuous volume, or open questions you cannot answer yet. | Discovery workshop recommended | The discovery workshop turns an unclear process into a written scope, or an honest no. |
| Anything moving money, even with approval. | Discovery workshop recommended | High-impact controls and limits are scoped by a person, in writing, first. |
Two worked examples
These are format illustrations composed for this page — not delivered projects, not client stories, and not evidence of prior work. They exist so you can see exactly what a brief looks like before you make one.
Worked example A — the weekly report nobody wants to assemble
Format illustration, not a delivered project: shows what a brief looks like for a clean fit.
Classification: Indicative fit: One Workflow, Properly Implemented. One trigger, one result, at most two listed systems, at a volume the fixed scope is built for.
- Trigger: A schedule (for example, every morning at 7:00)
- Read: Read the input from the source: An accounting or order system
- Check and shape: Validate the input, drop duplicates, and shape it into the agreed output format.
- Deliver: Produce the output (an internal record or report that stays inside the business) at the destination: A spreadsheet or CSV file
- Log and report: Record the run; on failure, retry per the agreed policy and alert a human with the error.
TradeLoom — workflow project brief Ruleset: tradeloom-scoper-v1 (deterministic template, not AI; not a binding quote) Problem: one repetitive process, described by the answers below. - Trigger: A schedule (for example, every morning at 7:00) - Source system: An accounting or order system - Destination system: A spreadsheet or CSV file - Output: An internal record or report that stays inside the business - Approval step: Runs happen on their own; a person reviews them regularly - Volume: A few times a week or less Task map (trigger to result): 1. Trigger — A schedule (for example, every morning at 7:00) 2. Read — Read the input from the source: An accounting or order system 3. Check and shape — Validate the input, drop duplicates, and shape it into the agreed output format. 4. Deliver — Produce the output (an internal record or report that stays inside the business) at the destination: A spreadsheet or CSV file 5. Log and report — Record the run; on failure, retry per the agreed policy and alert a human with the error. Assumptions: - You own or administer both systems and can authorize supervised access after contracting. - System credentials are never collected by this page or the inquiry form; access is arranged through a restricted process only after a signed scope. - The scope is one trigger-to-result workflow across at most two supported systems, within up to ten delivery hours; anything more is a separate written scope. - The workflow stays internal or staff-facing; anything that later goes outward gets an approval gate added to the scope. Unsupported requirements: none identified from these answers. Acceptance criteria skeleton (finalized per project in the written scope): - The workflow runs end-to-end on agreed test data, from the agreed trigger to the agreed output. - Retries and error handling are demonstrated with a deliberately failed run. - If anything goes outward, the approval gate is demonstrated: nothing is sent without a person approving it. - A runbook — how to run it, pause it, fix common failures and who to call — is handed over in a handoff session. Scope classification: Indicative fit: One Workflow, Properly Implemented Why: One trigger, one result, at most two listed systems, at a volume the fixed scope is built for. Your answers describe one trigger-to-result workflow across at most two listed systems at a volume the fixed scope is built for. The price for that scope is $1,250 — fixed — covering up to ten delivery hours with retries, error handling, acceptance tests, a runbook and a handoff session. This brief is not a binding quote: scope and price are confirmed in writing after a fit review. Sending this brief creates a routed inquiry only. It does not reserve time, and no price or scope is binding until a written scope is accepted by both sides.
Worked example B — the customer reply that must not send itself
Format illustration, not a delivered project: shows how a high-impact action gets an approval gate.
Classification: Indicative fit: One Workflow, Properly Implemented. One trigger, one result, at most two listed systems, at a volume the fixed scope is built for.
- Trigger: A new record — a form submission, order or booking
- Read: Read the input from the source: A form, booking or intake tool
- Check and shape: Validate the input, drop duplicates, and shape it into the agreed output format.
- Approval gate: Nothing is sent until a named person approves the run. This gate is mandatory for high-impact external actions.
- Deliver: Produce the output (a message to customers or partners) at the destination: An email inbox
- Log and report: Record the run; on failure, retry per the agreed policy and alert a human with the error.
TradeLoom — workflow project brief Ruleset: tradeloom-scoper-v1 (deterministic template, not AI; not a binding quote) Problem: one repetitive process, described by the answers below. - Trigger: A new record — a form submission, order or booking - Source system: A form, booking or intake tool - Destination system: An email inbox - Output: A message to customers or partners - Approval step: A person approves each run before anything is sent - Volume: Up to a few times a day Task map (trigger to result): 1. Trigger — A new record — a form submission, order or booking 2. Read — Read the input from the source: A form, booking or intake tool 3. Check and shape — Validate the input, drop duplicates, and shape it into the agreed output format. 4. Approval gate — Nothing is sent until a named person approves the run. This gate is mandatory for high-impact external actions. 5. Deliver — Produce the output (a message to customers or partners) at the destination: An email inbox 6. Log and report — Record the run; on failure, retry per the agreed policy and alert a human with the error. Assumptions: - You own or administer both systems and can authorize supervised access after contracting. - System credentials are never collected by this page or the inquiry form; access is arranged through a restricted process only after a signed scope. - The scope is one trigger-to-result workflow across at most two supported systems, within up to ten delivery hours; anything more is a separate written scope. - A named person on your side is available to approve runs before anything is sent. Unsupported requirements: none identified from these answers. Acceptance criteria skeleton (finalized per project in the written scope): - The workflow runs end-to-end on agreed test data, from the agreed trigger to the agreed output. - Retries and error handling are demonstrated with a deliberately failed run. - If anything goes outward, the approval gate is demonstrated: nothing is sent without a person approving it. - A runbook — how to run it, pause it, fix common failures and who to call — is handed over in a handoff session. Scope classification: Indicative fit: One Workflow, Properly Implemented Why: One trigger, one result, at most two listed systems, at a volume the fixed scope is built for. Your answers describe one trigger-to-result workflow across at most two listed systems at a volume the fixed scope is built for. The price for that scope is $1,250 — fixed — covering up to ten delivery hours with retries, error handling, acceptance tests, a runbook and a handoff session. This brief is not a binding quote: scope and price are confirmed in writing after a fit review. Sending this brief creates a routed inquiry only. It does not reserve time, and no price or scope is binding until a written scope is accepted by both sides.
Send your brief for a fit review
A person reads your brief and answers honestly — whether that's a written scope, a suggestion to start with the workshop, or a no. Sending a brief does not reserve time and creates no obligation on either side.
Send your question and keep the reference shown after it is saved. A saved request is not a confirmed appointment. Submitting this form does not reserve time and does not create a contract — a person confirms fit, scope and scheduling in writing first.
Prefer email? Email help@novahorizon.net. If this form is unavailable, email us directly.
Never paste passwords, API keys or other system credentials into this form. Access to your systems is arranged through a restricted process only after a signed scope.