Extensions

Staging Environment Setup

Try every change on a separate copy of your product first, so the live version customers use is never the test bed.

Editing prompts and settings straight on the live product means customers are the first to find your mistakes. This add-on gives the product you already run a separate staging copy. Your team edits and tries changes there, then promotes them to live through one documented step. Staging uses sandbox accounts where your providers offer them, so tests stay away from live systems.

Gives your team a safe copy to try changes
Promotes approved changes to live in one documented step
Uses sandbox accounts so tests stay away from live systems

$2,500 10–20 working days

Choose delivery and add to cart Ask an expert

Two matching wooden models, one being rearranged and one finished, changes tried on a copy before going live.

What it is

Staging Environment Setup is an add-on that gives an existing Upmark Labs product a separate staging copy for safe changes. Prompts, knowledge and settings can be edited and tried there, then promoted to live once approved. Promotion is one documented, repeatable step.

Why businesses buy it

A wrong prompt edit or a broken setting on a live agent can give customers bad answers for hours before anyone notices. Staging separates trying from releasing. Your team can experiment freely, a reviewer can approve the result, and the live product only changes when you decide. The written scope covers one staging environment, a documented promotion step, sandbox connections where available and testing with the parent product, so changes become routine rather than risky.

Problems this solves

Every change to prompts or knowledge is tried directly on the live product

This add-on gives the product a separate staging copy. Prompts, knowledge and settings can be edited and tried there first, while customers keep using the live version untouched.

A bad edit reaches customers before anyone spots it

Changes only reach live once someone approves them in staging. Mistakes can be found and fixed in the copy, before a single customer sees them.

Moving changes to live is fiddly and done differently each time

Promotion from staging to live is one documented, repeatable step. Admins follow the same short routine every time, and the updated documentation explains it in plain terms.

Scope card SKU UPM-A0038

Staging Environment Setup

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 a separate staging environment for safe changes
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

Changes are made straight on the live product today, and customers sometimes see the mistakes.

More than one person edits the product, and you want changes checked before they go out.

Your internal rules say changes must be tested away from production first.

The product is an Upmark Labs build, or you are ordering this with one.

Not the right fit if

You want answers checked automatically against known questions. Evaluation Test Suite does that, and works well alongside staging.

You want a person to approve the agent's actions, not your team's changes. Approval Workflow Layer covers it.

You want copies of your data kept safe, not a place to test. Offline Export and Backup schedules backups.

You want a record of who changed what. Audit Logging Add-on adds that trail.

How it works

The live setup is mapped. We list the parts of the product that change over time: prompts, knowledge, settings and connections.
A staging copy is built. It mirrors the live product, pointed at test accounts or sandbox connections where your systems offer them.
A promotion step is set up. Approved changes move from staging to live in a defined, repeatable way.
The round trip is tested. We make a change in staging, check it, promote it and confirm the live product behaves the same.
You review it with one revision round and receive updated documentation and a written walkthrough of the process.

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 a staging copy
Test or sandbox accounts for connected systems, where your providers offer them
Hosting access for the extra environment, in accounts in your name, shared securely as agreed at intake
Who may make changes in staging, and who approves promotion to live
One decision-maker for the setup

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

Timeline

Start Changeable parts and sandbox accounts listed

Weeks 1–2 Staging copy built to mirror live

Week 2 Promotion step from staging to live set up

Week 2 Full change round trip tested

Week 2 Your review and one revision round

Go-live Staging handed over with a written walkthrough

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

A separate staging environment for your existing product
A documented, repeatable step for promoting approved changes to live
Updated documentation and a test report
A handoff note and a short written walkthrough

Expected benefits and how to measure them

Helps keep customer-facing mistakes out of the live product
Can make admins more willing to improve prompts and knowledge
Makes releases more predictable

Live rollbacks: Count changes that had to be undone on live in the quarter before and after staging.
Issues caught in staging: Keep a short log of problems found in staging that never reached customers.
Changes released: Count approved changes promoted each month to see whether improvements happen more often.

Before you start: Note how changes are made today and how many caused problems in the last quarter.

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

Running costs

A second environment means some extra hosting, and testing in staging uses AI model calls. Both are billed to your own accounts. How much depends on how often you test; a quiet staging copy costs little.

Ask about running costs

Custom requirements

Several staging tiers, automatic promotion pipelines, or staging for systems outside the product are beyond this add-on. Describe them at checkout for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.

Request a custom version

Keep it running

Keeping staging in step with live is part of normal upkeep under the parent product's maintenance, which grows in line with the add-on's price.

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	A staging tier is often a higher subscription plan	An agency quotes it as infrastructure work	Ours is one fixed price, shown before you buy
Promotion	Often copy-and-paste between workspaces	Depends on the brief	Ours is a documented, repeatable step
Connections	May hit live systems	Set per project	Ours uses sandbox accounts where your providers have them

Questions about this product

What can I change in the staging copy?

Anything that normally changes on the product: prompts, knowledge sources, settings and flow rules. You try the change in staging, check how the product behaves, then promote it. Structural changes, such as a new connected system, still go through a Change Quote or an add-on.

Does staging talk to my real CRM or helpdesk?

Only if no test option exists. Where your providers offer sandbox or test accounts, staging connects to those so test changes never touch real records. Where they do not, we agree at intake how staging is limited, such as read-only access, before anything is connected.

How does a change move from staging to live?

Through a defined promotion step set up with you. Someone you name approves the change, and it is copied to live the same way every time. The written handover report and the documentation list every step in order, so anyone on your team can follow them.

Will staging double my running costs?

No. Staging only uses AI model calls when someone tests in it, and its hosting is usually small. Both sit in your own accounts. A team that tests a few changes a month adds little; heavy daily testing adds more. We talk you through the likely size at intake.

Can staging be added after our product has launched?

Yes. Staging is built as a copy of the product as it runs today, then kept in step through the documented promotion step. If you are buying the product now, staging follows its delivery speed. Faster speeds are available, each with a fixed price and date shown before you pay.

Should I pair staging with automated tests?

It helps. Staging gives you a safe place to change things; the Evaluation Test Suite tells you whether the change made answers better or worse. Together they let your team check a change thoroughly, on two fronts, before it ever reaches customers.