How the setup works

Start with one workflow. We map it, confirm access, build and test the first version, then deploy it with monitoring and maintenance.

01 · Start here

Bring one workflow, not a full spec.

Book the call or use the calculator. We turn the workflow into a clear map and fixed scope.

  • Pick the task you want off your plate first
  • Show where it happens today: Gmail, Sheets, CRM, WhatsApp, etc.
  • Leave with a scope, price range, and next steps

02 · What we need

Access, examples, and one decision owner.

No technical prep needed. We just need the tools involved and a few real examples.

  • Tool access - temporary or owner-approved access to the apps we connect
  • Sample work - real messages, rows, docs, or forms to test against

You keep the accounts and API keys. We guide the setup.

Approximate calculator

Build the first version of your setup.

Pick what the agent should touch. The estimate updates with setup range, timeline, maintenance, and what makes the build harder.

01

What should it handle?

Choose the work you want out of your hands first.

02

Connections

Documents, sheets, CRMs, and systems the agent reads from or writes to.

03

Communication and access

Where people talk to the agent and where your team controls it.

Expected use Choose the closest pattern, not a message count.

Client languages

Most Armenian businesses need at least two.

04

Difficulty knobs

Autonomy, model choice, usage pattern, and languages change testing time more than the button count does.

05

Complexity Level

L1 to L4 describes how much the agent can do without you approving each step.

What changes the number

The price rises when the agent has to make more promises.

01

Scope

One clean workflow is cheaper than five loosely connected ideas. We usually ship Phase 1 first, then expand.

02

Access

Google Sheets is simple. A custom CRM, payment tool, or unstable website needs more connection work.

03

Safety

Draft-only agents ship faster. Agents that send messages or update records need approval rules, logs, and edge-case testing.

04

Data shape

Clean folders and consistent sheets reduce build time. Messy files are fixable, but we budget for cleanup.

Before the call

A few useful answers.

How accurate is the calculator?

Accurate enough for planning, not for a contract. It estimates based on integrations, autonomy, volume, and testing complexity.

Can a setup really stay at 50,000 AMD?

Yes, if it is a small first workflow with a few common tools and human approval. Most real business setups rise from there.

What does maintenance include?

Bug fixes, small workflow changes, prompt tuning, provider updates, and keeping the agent working when APIs or tools change.

Who owns the accounts and data?

You do. The VPS, app accounts, API keys, and business data stay under your control. We configure the system around them.

Want the real quote?

Send the estimate or just tell us the workflow. We will map the build and give you a fixed number before anything starts.

Book a free 30-minute call