# Tell us the task, not the technology

> Describe one job you would hand to a capable new starter. We will tell you whether an agent should do it, what it would touch, and where a person still signs off.

Canonical page: https://aispeedforce.com/contact/

Last updated: 2026-09-22

Describe one job you would hand to a capable new starter. We will tell you whether an agent should do it, what it would read and write, and which decision still waits for a person.

## Start with one job

You do not need a spec. A paragraph about the work, the systems it lives in, and what currently goes wrong is enough for us to answer properly.

**Where it goes**: The form posts to a handler on this domain, which sends your inquiry to us as one email. No third-party form service in the middle, no tracking pixel, no CRM.

**Who reads it**: The person who would scope the build, not a sales desk. We reply to every inquiry, including the ones where the answer is that you do not need us yet.

**Helps most**: Name the systems by name. Shopify, HighLevel, a WordPress install, a spreadsheet somebody maintains by hand. It changes what we can tell you in the first reply.

## What happens after you send

Four steps, and you can stop at any of them. Nothing here is billed.

1. **It lands in one inbox**: The handler validates what you sent, then emails it to us with your address set as the reply-to. That is the whole journey.
2. **A person reads it and replies**: We reply to every inquiry. If the task is a poor fit for an agent, or for us, the reply says so and says why.
3. **We scope one task with you**: A short call to pin down the trigger, the records it reads and writes, the decision that waits for a human, and the eval cases we would judge it against.
4. **You get it in writing**: The scoped task, what the agent touches, the cost and latency ceiling we would build to, and what the first working version includes.

## Read first, write later

If you would rather see the shape of the work before you describe yours, start in one of these.

- [Agent engineering](https://aispeedforce.com/services/agent-engineering/)
- [Retrieval and data](https://aispeedforce.com/services/retrieval-and-data/)
- [Automation and workflows](https://aispeedforce.com/services/automation-workflows/)
- [Web development](https://aispeedforce.com/services/web-development/)
- [SEO](https://aispeedforce.com/services/seo/)
- [Platforms](https://aispeedforce.com/platforms/)
- [About](https://aispeedforce.com/about/)

## Before you write

### What should I put in the message?

One task, described the way you would describe it to a new starter. What sets it off, which systems it touches, what a finished run looks like, and the decision you would not want a machine making on its own. That is enough for us to answer.

### Do I need to know whether I want an agent?

No. Pick not sure yet and describe the work. Part of the reply is us saying when a scripted workflow or a plain integration does the job, and costs less to run than an agent would.

### Where does this form go?

To a handler on this domain, which sends your inquiry to us as one email. There is no third-party form service in the middle, no tracking pixel, and no CRM. We do not add you to a mailing list and we do not pass your details on.

## One task is enough to start

You do not need a plan for the whole stack. Pick the job that costs your team the most attention and describe that one.