WORK WITH ADAM / PRICING + PROCESS

WORK DIRECTLY WITH ADAM

You bring the problem. I build what fits.

A conversation can start with one annoying task, a rough product idea, or a screen recording of how the work happens now. I handle the technical decisions and give you one clear scope and flat quote.

Defined project phasesFixed pricesWritten completion checksAccounts you own

Choose by the problem

Which route sounds like today?

You do not need to know whether you need an agent, an API, or an app. Start with the thing you want to create or the work you need off your plate.

BUDGET GUIDANCE / NOT PACKAGES

Enough information to know whether we should talk.

There is one useful filter, not a menu of fixed packages. The real task determines the scope, and I will tell you directly when a smaller starting point makes more sense.

SMALLER FIRST STEP

AI Setup Session

$295 one-on-one · team sessions from $950Fixed scope · no larger commitment

Choose and configure the right AI tool, test one real task, and leave with reusable instructions in accounts you control.

CUSTOM AUTOMATION

One Repetitive Task

Full builds start at $2,500Most common first build

One real workflow—follow-up, intake, document checks, reports, or another repeatable pass—mapped, built, tested, and documented.

CONNECTED SYSTEMS

Connected Workflow

Larger custom scopeMultiple tools, rules, and approvals

Calls, inboxes, records, and actions connected across several tools, with custom rules, approvals, monitoring, and handoff.

CUSTOM SOFTWARE

App, Website, or Extension

Product scopeDesigned and shipped end to end

A custom mobile app, web app, website, browser extension, or internal tool with the core workflow, real users, production deployment, and launch foundation.

START WITH THE MESSY VERSION

Describe the work—not the software you think you need.

A rough explanation, a screen recording, or five real examples are enough. If an existing tool solves it better than a custom build, I will say that too.

START WITH A CONVERSATION

A rough note is enough.

You do not need to pick a product, diagnose the technology, or write a technical brief.

  1. 01You describe the idea or the work getting in the way.
  2. 02We work out whether existing tools or a build fit best.
  3. 03You get a clear next step before committing to work.
Tell me what you have in mind.

A quick note is enough. Adam reads every one personally.

PERSONAL REPLY · NO AUTOMATED SALES SEQUENCE

You can also email Adam your note.

Plain answers

Before you spend a call asking.

The basics should be visible. If something important is still unclear, email adam.preda@agentrunapps.com.

QUESTION

What should I budget?

For a full custom automation, plan on a minimum project budget of $2,500. Connected systems and custom apps can move into five figures. If that is more than you need, I can often start with a smaller setup, workshop, or tightly defined first step. Either way, you see the scope and one flat number before work begins.

QUESTION

When do I pay for custom work?

Start with a defined, fixed-price phase. Before work begins, we agree on its deliverables, completion checks, timeline, review window, and payment schedule. The written scope states any upfront payment and the balance due on completion. In-scope defects are corrected during the agreed review window; additional features or changes receive a separate quote. You can decide whether to commission another phase after reviewing the first. Any software, API, hosting, messaging, or account charges you approve in your own accounts are separate and identified before they are turned on.

QUESTION

Do I need to be technical?

No. You explain the business, the customer, or the work. I handle the technical decisions and explain what matters in plain English.

QUESTION

What if I only want to know what is possible?

That is a perfectly good first conversation. Sometimes the honest answer is that you should not build anything yet—and I will tell you that too.

QUESTION

Will I own it?

Yes. Your accounts, subscriptions, keys, sending identities, phone numbers, and data stay under your control throughout. When you accept and pay for custom work, the finished code, configuration, documentation, and system handoff are yours. The goal is ownership, not a dependency trap.

QUESTION

Am I buying one of the interfaces shown?

No. The recordings and blueprints make the behavior easy to inspect. Your implementation is designed around your actual workflow and normally runs inside the inbox, phone, CRM, accounting, calendar, job system, or social accounts you already own.

QUESTION

How do we work together?

You work directly with Adam from scope through launch. Small builds can take days; products take longer. The scope, timeline, price, and handoff are made clear before work begins.

QUESTION

What happens after launch?

Every accepted build includes a practical handoff and a defined fix window. Ongoing help is available when useful, but it is not required to keep ownership of accepted, paid work.

NO PITCH DECK REQUIRED

Bring the messy version of the problem.

We will find out whether there is a useful first build inside it. If there is, you get a clear scope and one flat price. Each custom phase has agreed deliverables, completion checks, and a payment schedule before work starts.