Extensions

Additional Workflow

Your AI product takes on one more defined job, built and tested like the ones it already does.

Once your AI product handles one job well, the next job is usually obvious: another document type, another request, another routine task. This add-on adds one more defined workflow, with its own trigger, steps and outcome, written down and agreed before the build. It runs on the product's existing connections and is tested with awkward real-world cases.

Adds one more defined job to your existing product
Agrees the trigger, steps and outcome in writing first
Tests awkward cases before the workflow goes live

$2,500 10–20 working days

Choose delivery and add to cart Ask an expert

Wooden marble run with one new piece slotted on the end, one more process added to a working system.

What it is

Additional Workflow is an add-on that adds one more defined workflow to an existing Upmark Labs product. The new workflow has its own trigger, steps and outcome, agreed in writing before the build. It fits workflow automations, action agents and document processing products.

Why businesses buy it

Extending a product that already works is faster and safer than starting a new one, because the connections, rules and testing are in place. The new workflow benefits from everything the product already knows. Without a written definition, though, new workflows tend to grow and surprise everyone. The scope fixes the trigger, steps, outcome and exceptions in writing, builds on existing connections and tests real-shaped cases, so you know exactly what the product will do before it starts doing it.

Problems this solves

Your product handles one process well but another stays manual

Additional Workflow adds one more defined workflow to your existing product. It has its own trigger, steps and outcome, so a second process can run alongside the first.

Vague automation requests turn into scope disputes later

The trigger, steps and outcome are agreed in writing before building starts. Everyone knows exactly what the new workflow will do, and just as clearly where it stops.

A new automation might clash with what already runs

The new workflow is tested together with the parent product before launch. The test report shows it running alongside your existing workflows without upsetting their steps.

Scope card SKU UPM-A0045

Additional Workflow

Everything this build includes, written down before you pay. Choose how you want it, own the code or license it yearly, then the delivery speed and any add-ons.

$2,500 one-time build price

What is included

Channel: As per the parent product
Integrations: As described in the add-on
Knowledge: As per the parent product
Workflows: Adds one more defined workflow to an existing AI product
Languages: As per the parent product
Testing: Tested together with the parent product
Revisions: 1 round
Handoff: Written handover report
Support: 14 days after launch

A good fit if

Your product works well, and there is one more process you want it to handle the same way.

You can describe the new workflow from start to finish: what starts it, what happens, what it produces.

The new workflow uses systems the product is already connected to.

The product is an Upmark Labs workflow automation, action agent or document processing build.

Not the right fit if

The new workflow needs a system the product is not connected to yet. Custom API or Webhook Integration adds the connection first.

You want a person to approve steps before they run. Approval Workflow Layer adds that check.

The new process spans many systems with several AI decisions. AI Multi-Step Workflow Automation is the bigger build.

Your product is a chatbot, voice agent or creative generator. This add-on fits workflow, action and document products.

How it works

The workflow is written down. Trigger, steps, decisions, outputs and what counts as done, agreed with you in plain language.
Exceptions are planned. What happens when data is missing, a system is down or a case does not fit the rules.
It is built into the existing product. The new workflow uses the same connections and settings as the others.
It is tested with real-shaped cases. We run sample cases, including awkward ones, and record the results.
You review the test report with one revision round, then get updated documentation and a written walkthrough.

What you provide within 72 hours

Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.

The order reference of the product getting the new workflow
A description of the workflow, with an example of a typical case
The rules or decisions the workflow must follow
Sample data or documents for testing, including a few awkward cases
One person who approves the written workflow

The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.

Timeline

Start Workflow description and sample cases received

Week 1 Workflow and exceptions written and agreed

Weeks 1–2 Workflow built into the existing product

Week 2 Sample cases run, test report written

Week 2 Your review and one revision round

Go-live Workflow live, walkthrough recorded

Delivery options, in working days (Monday to Friday) from completed intake. They can extend because of national or public holidays, technical issues outside our control (such as platform outages, third-party changes, account approvals or access delays), or natural disasters and other events beyond our control. If a delay happens, we tell you in writing with a new date.
Option	Delivery time	Price
Standard	10–20 working days	$2,500

What you receive at handover

One more workflow running in your existing product
A written definition of its trigger, steps and outcome
Updated documentation and a test report
A handoff note and a short written walkthrough

Expected benefits and how to measure them

Can take another manual process off your team's plate
Helps keep automation scope clear
Makes it easier to add processes one at a time

Time on the process: Ask staff to note weekly time spent on the process before launch and a month after.
Workflow runs: Count successful runs from the product's logs each week.
Errors or exceptions: Track failed runs and manual corrections each month.

Before you start: Time how long the process takes by hand now and how often it runs each week.

These are things to track, not promised results. Outcomes depend on your data, your team and your market.

Running costs

The new workflow adds usage in proportion to how often it runs, billed to your own AI and platform accounts like the rest of the product. A workflow that runs rarely adds little.

Ask about running costs

Custom requirements

A workflow that needs a new system connection, or more than one new workflow, is quoted separately or ordered as further add-ons. Add a checkout note for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.

Request a custom version

Keep it running

Once live, the new workflow joins the parent product's maintenance, which grows in line with this add-on's price. Small rule changes come out of the monthly change hours, and the allowance grows as the product runs more workflows.

Adds $125/mo to maintenance

Covered by the main product's maintenance, which grows by this amount.

How maintenance works

How this compares

	Do it yourself with a SaaS tool	Hire a custom agency	Upmark Labs
Price	Automation tools often charge more per task or step	An agency quotes each new process separately	Ours is one fixed price, shown before you buy
Definition	You build and maintain it yourself	Depends on the brief	Ours is written and agreed before the build
Exceptions	Often discovered in production	Set per project	Ours are planned and tested with awkward cases

Questions about this product

What counts as one additional workflow?

One process with a single trigger, a defined set of steps and a clear outcome, using systems the product already connects to. For example, a new document type routed and filed, or one new kind of request handled end to end. If your description covers several processes, we will say so before you pay.

Can the new workflow use a system we have not connected?

Not within this add-on. The workflow is built on the product's existing connections. If it needs a new system, add Custom API or Webhook Integration or a matching integration add-on, and both can be delivered in the same order. We confirm which applies at intake.

Which products can take an Additional Workflow?

Workflow automations, action agents and document processing products. Those are built around defined workflows or actions, so one more fits naturally. Conversational products add call or chat flows in a different way, and creative products are not structured around workflows, so this add-on does not apply to them.

How do you test the new workflow?

With sample cases you provide, shaped like real ones, including a few awkward cases such as missing data or an unusual request. Each run is recorded in a test report showing the input, the steps taken and the result. You review it before launch and can ask for one round of changes.

Can several Additional Workflows be ordered at once?

Yes. Each workflow is a separate add-on with its own written definition and tests, and several can be delivered in the same order. They follow the delivery speed chosen for the product, and faster speeds are available, each with a fixed price and date shown before you pay. Describe each workflow clearly at intake.

Can I add more than one workflow at a time?

Yes, by adding this add-on once for each workflow. Each one is defined, built and tested separately, so the scope stays clear. If the workflows are closely linked, mention it in the checkout note and we confirm whether they really count as one or several.

Give your product one more job to do.

Add an Additional Workflow and one more process is written down, built on your existing connections and tested with real-shaped cases before it goes live.

Add to cart Ask an expert See all add-ons