# Engagements & pricing > Try one job with an Agent Test Drive, start with one engineering capability or a focused solution, or have Sidekick build a complete digital AI co-worker. Source: https://sidekickmachines.com/pricing/ Engagements & pricing ## Buy the work you need done. Start with a focused engagement. We agree the scope, deliverables, acceptance criteria and price before implementation. [Ask about a Test Drive](mailto:hello@sidekickmachines.com?subject=Agent%20Test%20Drive\&body=Hello%20Sidekick%2C%0A%0AWe%20would%20like%20to%20try%20an%20Agent%20Test%20Drive.%0A%0AJob%20we%20have%20in%20mind%3A%0A%0APeople%20who%20would%20work%20with%20it%3A%0A%0ADecisions%20that%20should%20stay%20with%20a%20person%3A%0A) What a Test Drive includes 1. ### One capability. Bring in specialist engineering for a defined need such as memory, MCP tooling, evals or identity. [Explore capabilities](https://sidekickmachines.com/capabilities/) 2. ### A focused solution. Combine the capabilities needed to reach an outcome, such as production readiness or stronger operating controls. [Explore solutions](https://sidekickmachines.com/solutions/) 3. ### A complete digital AI co-worker. Have Sidekick build the agent around its job and agree the ongoing operation with your team. [Explore Complete digital AI co-workers](https://sidekickmachines.com/ai-teammates/) Agent Test Drive ### Try one job, live in your Microsoft Teams. One digital AI co-worker takes on one job in your Microsoft Teams for a set period. Your people work with it on real tasks. Then you decide what happens next. - One job - One digital AI co-worker - A set period - Fixed size - Fixed price, agreed up front [Ask about a Test Drive](mailto:hello@sidekickmachines.com?subject=Agent%20Test%20Drive\&body=Hello%20Sidekick%2C%0A%0AWe%20would%20like%20to%20try%20an%20Agent%20Test%20Drive.%0A%0AJob%20we%20have%20in%20mind%3A%0A%0APeople%20who%20would%20work%20with%20it%3A%0A%0ADecisions%20that%20should%20stay%20with%20a%20person%3A%0A) What you get 1. #### A written job description What your agent does, which systems it uses and which decisions stay with a person. 2. #### Its approval rules Which actions wait for a person, and who approves each one. 3. #### Your agent, live in Microsoft Teams Your people hand it real tasks, follow its progress and make decisions. 4. #### A closing review What it did, where your people stepped in and what could come next. #### Then you decide - Keep it running with us: It stays at work. We run it every day and report what it did. - Grow it: More of its job, or a second job. - Stop: We switch it off. Two ways we work ### Build it with us, or let us run it. We recommend letting us run it: people who built your agents know them best. Either way, your agents run in your cloud and your people approve sensitive actions. - #### Inside your team Our engineers work with yours, in your environment. We build your agents together, and your team runs them after handover. Who does what - Build Sidekick and Your team - Run Your team - Approve Your people Best for: Teams that want to run agents themselves, with specialists alongside. - Recommended #### We run it for you We build your agents and keep them running: watching their work, fixing issues and adding skills as your needs grow. [See agent operations](https://sidekickmachines.com/agent-operations/) Who does what - Build Sidekick - Run Sidekick - Approve Your people Best for: Teams that want agents at work without building an agent engineering team of their own. No SaaS. Zero bits flow to us. You keep 100% of everything, keys included. [See trust and security](https://sidekickmachines.com/trust/) How an engagement typically runs ### From job to running agent. Each engagement agrees its own scope and pace up front. Its phases usually look like this. 1. #### Define a job and its approvals We write down what your agent does, which systems it uses, which actions wait for a person and how we’ll know it works. 2. #### Build with approvals in place We give your agent its own identity, connect just those systems its job needs and set its approval rules before it touches real work. 3. #### Run on real work Once it passes agreed checks, it goes live in Microsoft Teams, where your people hand it real tasks and approve its sensitive steps. 4. #### Keep running or hand over We keep it running for you, or your team takes it over with a runbook and a handover session. Adoption #### People named before go-live. Each engagement answers three questions with you, so your people know how to work with their agent. - ##### Who uses it Which people hand it work and read its updates in Microsoft Teams, and how they learn to work with it. - ##### Who approves Who signs off each kind of sensitive action, and who covers when they’re away. - ##### Who looks after it Who watches its work, handles exceptions and reviews changes after handover. What you get ### Written down, tested, walked through. With each agent we build, inside your team or run by us. 1. #### Job description What your agent does, which systems it uses and which decisions stay with a person. 2. #### Approval rules Which actions wait for a person, and who approves each one. 3. #### Test results before go-live How your agent did on agreed checks, before it goes to work. 4. #### Runbook How to watch its work, handle exceptions and make changes. 5. #### Handover session Time with your team to walk through all of it. What shapes the scope ### Specific work. Clear terms. - The agent’s current state and the outcome you need. - The systems, data, authentication and deployment constraints involved. - The evidence required for acceptance and the handoff your team needs. - Any ongoing support or operation, plus infrastructure and model costs. FAQ ### Questions, answered. #### How do we start? With one job. Tell us about it, and we’ll suggest where to begin: an Agent Test Drive, one capability, a focused solution or a complete digital AI co-worker. Scope, deliverables, acceptance criteria and price are agreed before any work begins. #### What does an Agent Test Drive include? One job and one digital AI co-worker, live in your Microsoft Teams for a set period. You get a written job description, its approval rules, your agent at work with your people on real tasks and a closing review of what it did and what could come next. Its size and price are fixed and agreed up front. #### What happens after a Test Drive? You decide. Keep it running with us, grow it into more of its job or a second job, or stop. Keeping or growing it becomes a regular engagement, with its scope and price agreed up front. #### Do agents run in our environment? Yes. Your agents run in your cloud, where your data lives, and your people reach them in Microsoft Teams. Our engineers work inside your environment. #### Who approves what agents do? Your people. Each agent can use just those systems and actions approved for its job. Sensitive actions wait for a person to approve that exact request, you can stop any agent at any time, and everything it does is on record. #### Who looks after an agent after go-live? We do, if you choose, and we recommend it: people who built your agent know it best. We watch its work, fix issues and add skills as your needs grow. Or your people take it over with a runbook and a handover session. #### Can we start with one capability instead? Yes. Each capability is available on its own, from agent security to evals and memory. Bring a specific need, and we’ll agree its scope with you. #### How is pricing set? Every engagement has a price agreed up front, based on its scope: your agent’s job, systems and data involved, evidence needed for acceptance and any ongoing operation. An Agent Test Drive has a fixed size and a fixed price. A useful place to start ### Let’s get your agents into production. Bring us one problem. We’ll work out the right engagement with you. [Talk it through](https://sidekickmachines.com/contact/)