{"name":"AI Agentship","version":"1.0","updated":"2026-10-19","canonical":"https://www.aiagentship.com/","pages":[{"path":"/","title":"AI-Native Workspace for Human + AI Teams | AI Agentship","description":"Build your human + AI workspace. Forward-Deployed Operators connect knowledge, tools, and review around Time-to-Value (TTV). Start free.","url":"https://www.aiagentship.com/","content":"# AI Agentship\n\n## Build the workspace for your (Human + AI) team\n\nBecome a Forward-Deployed Operator: the person who builds and runs AI-native operations. Organize business knowledge, connect tools, and give AI agents the workspaces, instructions, and tasks they need to prepare research, reports, dashboards, and operational work for human review.\n\n## Our focus: Time-to-Value (TTV)\n\nShorten Time-to-Value (TTV) with a Forward-Deployed Operator.\n\nTime-to-Value (TTV) is the time it takes to reach a useful business result. A Forward-Deployed Operator works alongside your team to define that result, remove implementation blockers, and build the workflow that delivers it.\n\nWe organize company knowledge, connect approved tools, define agent tasks, and put review and ownership into the process. Then we test the result against the standard you agreed before expanding.\n\nFor the first deployment, measure TTV from the agreed kickoff to the first result verified by the workflow owner. Track quality, total delivery cost, and human review effort alongside elapsed time.\n\nKeep improving until the team can repeat the result in everyday work.\n\n## Your team has AI tools. Where is the first valuable result?\n\nThe gap between AI capability and useful work is an operating problem: unclear outcomes, scattered knowledge, disconnected tools, and no agreed review path. These blockers extend Time-to-Value (TTV). A Forward-Deployed Operator works inside the business to remove them and give the team a clear path from kickoff to a verified result.\n\n## Forward deployed operator builds the system between AI and value.\n\nStart with one valuable result. Your Forward-Deployed Operator organizes company knowledge, connects approved tools, and defines the agent tasks, human decisions, and review that make it possible. Time-to-Value (TTV) tracks the path from the agreed kickoff to the first verified outcome. The next step is making that result repeatable in everyday work.\n\n## Rajiv Bhusal - Forward Deployed Operator\n\nAs AI agents take on more technical work, Forward-Deployed Operators organize the people, knowledge, and systems that turn that work into business value and shorten the time it takes to get there.\n\nPeople define the outcomes, set standards, and make consequential decisions. The operator connects company knowledge, approved tools, agent tasks, and human review around those outcomes. Time-to-Value (TTV) measures the path from the agreed kickoff to the first verified result; quality, delivery cost, and repeated use show whether that value lasts.\n\n## Plans and support\n### Forward Deployed Operator — Free \nExplore how people and agents share knowledge, tasks, and reviewed outputs in a Notion workspace. Includes a sample workflow and setup guide; connect your own systems separately.\n- Notion workspace for business knowledge, agent tasks, and reviewed outputs\n- Company brain starter and agent-ready templates\n- Sample workflow and agent instructions\n- Example output and review checklist\n- Setup guide\n- Sample data; tool connections require configuration\nLink: https://whop.com/ai-agentship-com/forward-deployed-operator/\n\n### Forward Deployed Operator Pro — $230 one-time\nBuild toward shorter Time-to-Value (TTV) with reusable workspaces, agent instructions, configuration guides, and evaluation templates. You configure and test the implementation.\n- Notion workspaces and workflow templates\n- Agent instructions and reusable skill files\n- Configuration guides and sample outputs\n- Task, evaluation, and review templates\n- Knowledge, research, reporting, and agent operations systems\n- You configure, build, and test your implementation\nLink: https://whop.com/ai-agentship-com/forward-deployment-operator-pro/\n\n### AI Implementation Support — $500 /month\nGet guidance while you define the first valuable result, build the workflow, and test it. Weekly coaching and reviews support your implementation; custom development is scoped separately.\n- Weekly coaching\n- Workflow and configuration reviews\n- Troubleshooting within the agreed scope\n- Feedback on testing and handover\n- You carry out the implementation\n- Custom development is scoped separately\nLink: https://whop.com/ai-agentship-com/ai-implementation-support/\n\n## Custom implementation\nImplementation is priced after we agree the workflow, data sources, tool access, acceptance checks, and handover. Ongoing operation is arranged separately. Third-party software and AI usage are separate.\nContact: https://calendly.com/chat-aiagentship/30min\n\n## Questions and answers\n### What is a Forward-Deployed Operator (FDO)?\nAt AI Agentship, a Forward-Deployed Operator works inside the business to turn an AI opportunity into a working, adopted workflow. Their focus is Time-to-Value (TTV): connecting business understanding, hands-on implementation, and operational ownership to help the team reach a verified result and repeat it. Ongoing responsibilities are agreed for each engagement.\n\n### Who is the Forward Deployed Operator workspace for?\nFounders and operational teams in agencies, professional firms, and companies building human + AI workflows. Start with recurring research, reporting, onboarding, or client-delivery work. Use shared knowledge, clear agent tasks, and human review to work toward a result the team can verify.\n\n### What does AI-native operations mean?\nDesigning how work happens so AI agents can use structured business knowledge, follow instructions, run defined tasks, and work through connected tools. The FDO builds and maintains that operating system; people set priorities, approve consequential actions, and review outputs.\n\n### What is included in the free Forward Deployed Operator workspace?\nA Notion workspace for organizing business knowledge, agent tasks, and reviewed outputs, with agent-ready templates, a company brain starter, a sample workflow, and a setup guide. It uses sample data and is not connected to your business tools.\n\n### What is the difference between the workspace and Forward Deployed Operator Pro?\nThe free workspace introduces the structure and a sample workflow. The Forward Deployed Operator Pro expands it with workspaces, workflow templates, reusable agent instructions and skills, configuration guides, sample outputs, and evaluation templates. Forward Deployed Operator Pro is $230 one-time. See its Whop page for included systems and purchase terms.\n\n### Do I need to be an engineer to become an FDO?\nYou can explore the workspace and learn the operating method without engineering experience. Connecting business tools may require API configuration, coding, or technical assistance. An FDO combines operational understanding with the implementation skills needed for the chosen workflow.\n\n### Are the AI agents already connected to our systems?\nNo. The workspace and pack provide structures, instructions, and examples built for AI agents. Your FDO needs to configure the data, tools, permissions, and review paths, then test the workflow before live use.\n\n### What does AI Implementation Support include for an FDO?\nSupport is $500/month for weekly coaching, workflow and configuration reviews, troubleshooting within the agreed scope, and feedback on testing and handover. You implement with guidance. Confirm coaching format and support limits before subscribing. Custom development and third-party software or AI usage are separate.\n\n### Can an FDO implement a fully custom system for us?\nYes. Bring one workflow and its responsible owner. We agree the first-value milestone, baseline, acceptance checks, and scope; prepare knowledge and approved tool connections; then test real work and document handover. Custom implementation is priced separately, and ongoing operation is agreed for the engagement.\n\n### How does an FDO review and improve AI agent work?\nDefine approved sources, access boundaries, output checks, and a human reviewer. Track tasks, outputs, exceptions, costs, and evaluations. Record corrections, update instructions, and test changes on representative work. Review helps inspect the output; it does not guarantee correctness.\n\n### Can an FDO work inside an AI SaaS company or AI agency?\nYes. We work with AI SaaS companies and AI agencies that want an FDO working in their business. That can include internal AI-native operations, customer onboarding, agent-ready workspaces, and client delivery. Agree responsibilities, access, communication, review, and support scope before the engagement.\n\n### How do you measure Time-to-Value (TTV) from AI?\nTime-to-Value (TTV) measures how long it takes to reach an agreed business outcome. For an initial deployment, we measure time to first verified value: elapsed time from the agreed engagement kickoff to the first result verified by the workflow owner. Define the milestone, baseline, quality standard, and cost limits before building. For example, a real client report is accepted and used, meets the standard, and demonstrates less preparation and review effort than comparable baseline work. Keep access delays and unfinished work visible; a demo or connected tool alone is not proof of value.\n\n### Do you guarantee a fixed Time-to-Value (TTV)?\nNo. The focus is a clear path to measurable value, not a guaranteed number of days or percentage improvement. Timing depends on the workflow, data, access, decisions, and adoption. Track quality, total cost, review and rework alongside the first milestone, then check whether the team can repeat the result. Exploring the free sample workspace is not the same as reaching value in a live business workflow.\n\n## Practical guides\n- [What is a Forward-Deployed Operator?](https://www.aiagentship.com/guides/forward-deployed-operator)\n- [How do you build AI-native operations?](https://www.aiagentship.com/guides/ai-native-operations)\n- [What makes a workspace ready for AI agents?](https://www.aiagentship.com/guides/agent-ready-workspace)\n- [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\n- [Forward-Deployed Operator vs Engineer: FDO and FDE compared](https://www.aiagentship.com/guides/forward-deployed-operator-vs-engineer)\n- [AI implementation roadmap: from pilot to verified value](https://www.aiagentship.com/guides/ai-implementation-roadmap)\n- [AI workflow automation: build a useful agentic workflow](https://www.aiagentship.com/guides/ai-workflow-automation)\n- [AI reporting for agencies: automate preparation, keep review](https://www.aiagentship.com/guides/ai-reporting)\n- [AI knowledge base: build a company brain agents can use](https://www.aiagentship.com/guides/ai-knowledge-base)\n\nSource: https://www.aiagentship.com/\nUpdated: 2026-10-19\n","language":"en"},{"path":"/guides","title":"AI Implementation, FDO & TTV Guides | AI Agentship","description":"Practical guides to Forward-Deployed Operators, Time-to-Value (TTV), and human + AI workflows with shared knowledge, approved tools, and review.","url":"https://www.aiagentship.com/guides","content":"# Practical FDO guides\n\n## [What is a Forward-Deployed Operator?](https://www.aiagentship.com/guides/forward-deployed-operator)\nAt AI Agentship, a Forward-Deployed Operator (FDO) works alongside a business to turn an AI opportunity into a working, adopted workflow. They define the first valuable result, organize knowledge, connect approved tools, configure agent tasks, and help people verify and repeat the outcome.\n\n## [How do you build AI-native operations?](https://www.aiagentship.com/guides/ai-native-operations)\nAI-native operations means designing business work so AI agents can use structured knowledge, follow defined instructions, run tasks through approved tools, and prepare outputs people can review. A Forward-Deployed Operator connects these pieces and helps the operational team run the system.\n\n## [What makes a workspace ready for AI agents?](https://www.aiagentship.com/guides/agent-ready-workspace)\nAn agent-ready workspace gives AI agents a consistent place to find business knowledge, receive tasks, follow instructions, record outputs, and request human review. It makes the work readable and actionable for agents while keeping ownership and decisions visible to people.\n\n## [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\nTime-to-Value (TTV) measures the elapsed time between a defined starting event and a useful business outcome. For an initial AI deployment, AI Agentship measures from the agreed kickoff to the first result verified by the workflow owner. Define the outcome before building and track quality, cost, and review effort alongside speed.\n\n## [Forward-Deployed Operator vs Engineer: FDO and FDE compared](https://www.aiagentship.com/guides/forward-deployed-operator-vs-engineer)\nForward-Deployed Engineers usually emphasize building technical solutions inside a customer environment. At AI Agentship, Forward-Deployed Operators emphasize connecting the business workflow, systems, people, and adoption around a verified outcome. The roles overlap, titles vary, and complex implementations may need both engineering depth and operating ownership.\n\n## [AI implementation roadmap: from pilot to verified value](https://www.aiagentship.com/guides/ai-implementation-roadmap)\nAn AI implementation roadmap connects a business outcome to the knowledge, tools, agent tasks, evaluation, and adoption needed to deliver it. Start with one real workflow and an agreed first-value milestone. Expand only after the owner accepts the result and the team can repeat it within quality, cost, and permission boundaries.\n\n## [AI workflow automation: build a useful agentic workflow](https://www.aiagentship.com/guides/ai-workflow-automation)\nAI workflow automation uses models for tasks such as interpreting information, extracting fields, or drafting within a business process. An agentic workflow can also choose steps or tools within defined boundaries. Use deterministic automation for predictable rules and calculations, and retain explicit ownership, review, and exception handling around AI decisions.\n\n## [AI reporting for agencies: automate preparation, keep review](https://www.aiagentship.com/guides/ai-reporting)\nAI reporting combines reliable data preparation with model-assisted summaries, explanations, and report drafts. For agencies and professional firms, a useful system keeps metric definitions, sources, client context, and human approval together. The goal is an accepted report that supports client work, not simply a document generated faster.\n\n## [AI knowledge base: build a company brain agents can use](https://www.aiagentship.com/guides/ai-knowledge-base)\nAn AI knowledge base makes approved business information retrievable by people and AI systems. A useful company brain includes source ownership, dates, permissions, definitions, and reviewed examples. Retrieval can ground a response in company content, but it does not guarantee accuracy, current information, or permission enforcement by itself.","language":"en"},{"path":"/guides/forward-deployed-operator","title":"What is a Forward-Deployed Operator? | AI Agentship","description":"Understand the FDO role: define a first valuable result, remove blockers, build AI workflows, verify value, and help the team repeat it.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/forward-deployed-operator","content":"# What is a Forward-Deployed Operator?\n\nAt AI Agentship, a Forward-Deployed Operator (FDO) works alongside a business to turn an AI opportunity into a working, adopted workflow. They define the first valuable result, organize knowledge, connect approved tools, configure agent tasks, and help people verify and repeat the outcome.\n\n## Start with the work and its owner\n\nChoose one recurring business task. A useful first task has an identifiable input, a named owner, and an output someone already needs. A weekly client report, an onboarding brief, or a research update makes the scope easier to inspect than a goal such as automate the company.\n\nMap the current process before configuring an agent. Record where information comes from, what judgment is involved, who can approve an action, and what happens when information is missing. The FDO works with the operational team to make those responsibilities explicit.\n\n## Build the system the agent works in\n\nPrepare approved business documents, definitions, examples, and task instructions. Put the inputs, expected output, tool access, and review requirements in a consistent structure. This gives an agent usable context rather than a collection of disconnected prompts.\n\nConfigure only the connections the task needs. A research workflow might read approved documents and prepare a brief. A reporting workflow might read a spreadsheet, apply agreed metric definitions, and draft an update. Actions that change business records need their own permissions and approval rules.\n\n## Test, hand over, and improve\n\nTest representative examples and failure cases: missing documents, stale data, contradictory sources, unavailable tools, and incomplete outputs. Review accuracy, completeness, operating cost, and the work a person still needs to do. Define acceptance checks before calling the workflow ready.\n\nDocument how to run the task, check the output, handle exceptions, and stop or recover the workflow. Train the responsible owner. Record corrections and retest changes to instructions, knowledge, or tools; repeated use alone does not guarantee that an agent improves.\n\n## Measure Time-to-Value (TTV)\n\nAgree the workflow, owner, baseline, acceptance standard, and cost limits before building. For the first deployment, measure Time-to-Value (TTV) as elapsed time from engagement kickoff to the first useful business result verified by that owner. A connected API, completed demo, or duplicated workspace alone is not evidence of value.\n\nFor example, a real client report is accepted and used, meets the agreed quality standard, and demonstrates lower preparation and review effort than comparable baseline work. Keep access delays, scope changes, and unfinished engagements visible. Track total cost, quality, and rework alongside elapsed time, then verify that the team can repeat the result. Timing depends on the workflow; no fixed delivery time or improvement is guaranteed.\n\n## Choose a practical starting point\n\nExplore the free Forward Deployed Operator workspace to understand an agent-ready Notion structure on sample data. Forward Deployed Operator Pro expands the templates, instructions, and configuration guides for builders. AI Implementation Support provides coaching while you implement. Fully custom implementation is scoped separately.\n\nYou do not need engineering experience to inspect the sample workspace. Connecting live tools can require API configuration, coding, or technical assistance. Pick the support level around the actual workflow and the implementation skills your team has.\n\n## Implementation checklist\n- Define the first-value milestone and baseline.\n- Name the task and its owner.\n- Define inputs, output, permissions, and review.\n- Prepare approved context and examples.\n- Test normal work and failure cases.\n- Document operation and train the owner.\n\n## Sources and further reading\n- [TSIA: forward-deployed roles and operating outcomes](https://www.tsia.com/blog/forward-deployed-engineering-ai-era)\n- [Gainsight: defining Time-to-Value](https://www.gainsight.com/glossary/entry/customer-onboarding-metrics/)\n\n## Keep learning\n- [How do you build AI-native operations?](https://www.aiagentship.com/guides/ai-native-operations)\n- [What makes a workspace ready for AI agents?](https://www.aiagentship.com/guides/agent-ready-workspace)\n- [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\n\nSource: https://www.aiagentship.com/guides/forward-deployed-operator\n\nPublished: 2026-10-14\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/ai-native-operations","title":"How do you build AI-native operations? | AI Agentship","description":"A practical method for organizing knowledge, agent tasks, connected tools, human review, and improvement around real business work.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/ai-native-operations","content":"# How do you build AI-native operations?\n\nAI-native operations means designing business work so AI agents can use structured knowledge, follow defined instructions, run tasks through approved tools, and prepare outputs people can review. A Forward-Deployed Operator connects these pieces and helps the operational team run the system.\n\n## Choose one workflow before expanding\n\nStart where repeated preparation is visible: collecting client intake information, assembling a weekly status report, updating a research brief, or checking a dashboard. Describe the result in business terms and name the person responsible for accepting it.\n\nRecord a baseline for preparation time, review and rework effort, turnaround, and total cost per accepted deliverable. Define the first business result worth reaching, then compare real work with that baseline using similar examples. Use Time-to-Value (TTV) to track time from kickoff to the first result verified by its owner. A polished demonstration does not establish business value or operating reliability.\n\n## Give agents knowledge and bounded tools\n\nOrganize methods, source definitions, process notes, and reviewed examples into a company knowledge structure. Keep source dates and ownership visible so the reviewer can identify stale or conflicting information. Use task-specific context instead of granting every agent access to every document.\n\nConnect the tools required by the workflow through the interfaces they support, including APIs or MCP where appropriate. Match access to the task. Read-only access is often a useful first step for research or reporting; permissions to send messages or change records need separate consideration.\n\n## Make task state and review visible\n\nEach task needs an owner, its current state, an expected output, and a review path. Record the sources used, actions taken, exceptions found, and what remains unresolved. These records help the operational team understand what an agent prepared and what needs a decision.\n\nFor example, an agent preparing a client report can collect approved updates, draft the report in the agreed format, and flag missing figures. A person checks the figures and conclusions before delivery. The workflow should show an incomplete result when inputs are missing rather than quietly inventing them.\n\n## Run an improvement loop\n\nReview a representative set of completed tasks. Track useful measures such as completeness, source accuracy, exceptions, review time, and usage cost. Save corrections, update the relevant knowledge or instructions, and rerun the checks before applying the change to live work.\n\nExpand to another function only when ownership, access, and acceptance checks are clear. The same structure can support company operations, agency delivery, or professional-firm research and reporting, but the workflow and its review responsibilities still need to be configured for that business.\n\n## Implementation checklist\n- Pick a repeated task with a measurable baseline.\n- Organize approved knowledge for that task.\n- Connect tools with appropriate access.\n- Track tasks, outputs, and exceptions.\n- Review, correct, and retest before expanding.\n\n## Sources and further reading\n- [IBM: agentic workflows and automation](https://www.ibm.com/think/topics/agentic-workflows)\n\n## Keep learning\n- [What is a Forward-Deployed Operator?](https://www.aiagentship.com/guides/forward-deployed-operator)\n- [What makes a workspace ready for AI agents?](https://www.aiagentship.com/guides/agent-ready-workspace)\n- [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\n\nSource: https://www.aiagentship.com/guides/ai-native-operations\n\nPublished: 2026-10-14\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/agent-ready-workspace","title":"What makes a workspace ready for AI agents? | AI Agentship","description":"Learn how structured knowledge, task briefs, agent instructions, permissions, output records, and review queues make a workspace usable by agents.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/agent-ready-workspace","content":"# What makes a workspace ready for AI agents?\n\nAn agent-ready workspace gives AI agents a consistent place to find business knowledge, receive tasks, follow instructions, record outputs, and request human review. It makes the work readable and actionable for agents while keeping ownership and decisions visible to people.\n\n## Use a consistent structure\n\nCreate clear places for company knowledge, task records, instructions, outputs, and evaluations. Use stable names and explicit fields. A task brief should explain the goal, input sources, expected output, available tools, approval boundary, and responsible reviewer.\n\nA workspace is not automatically connected because it contains agent instructions. The agent runtime must be configured to read the intended sources and write to approved destinations. Test those connections with sample data before using business information.\n\n## Prepare business context for retrieval\n\nOrganize approved documents, metric definitions, examples, methods, and process notes. Include enough context for the agent to understand the task and for a person to verify the result. Identify who maintains a source and how updates reach the workflow.\n\nKeep client boundaries and access requirements explicit. A shared template does not itself isolate client data or enforce tool permissions. Those controls must be configured in the workspace, connected systems, and runtime used for the implementation.\n\n## Store outputs with review context\n\nKeep the draft, supporting sources, unresolved questions, and action record together. Give reviewers a clear way to approve, request a correction, or mark the result incomplete. For research, reports, and dashboards, evidence and definitions should travel with the output.\n\nRecord failures as well as successful runs. Missing inputs, permission errors, unavailable tools, and conflicting sources are useful operating signals. An agent-ready system should make exceptions visible so a person can decide what happens next.\n\n## Explore the free Forward Deployed Operator workspace\n\nThe free Forward Deployed Operator workspace is a Notion starting point for business knowledge, agent tasks, and reviewed outputs. It includes a sample workflow and setup guide so you can inspect the structure before adapting it to a real task.\n\nThe sample uses sample data and is not connected to your tools. Forward Deployed Operator Pro adds reusable systems and configuration material for builders. Technical configuration, third-party subscriptions, model usage, and any custom implementation remain separate from simply duplicating a workspace.\n\n## Implementation checklist\n- Define stable knowledge, task, and output structures.\n- Write instructions with clear input and output requirements.\n- Configure tools and permissions explicitly.\n- Keep sources and exceptions beside each output.\n- Assign a human owner for review and maintenance.\n\n## Sources and further reading\n- [Microsoft Learn: retrieval, source access, and governance](https://learn.microsoft.com/en-us/azure/search/retrieval-augmented-generation-overview)\n\n## Keep learning\n- [What is a Forward-Deployed Operator?](https://www.aiagentship.com/guides/forward-deployed-operator)\n- [How do you build AI-native operations?](https://www.aiagentship.com/guides/ai-native-operations)\n- [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\n\nSource: https://www.aiagentship.com/guides/agent-ready-workspace\n\nPublished: 2026-10-14\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/time-to-value","title":"Time-to-Value (TTV): definition, formula, and AI examples | AI Agentship","description":"Measure Time-to-Value from kickoff to a verified AI outcome. Includes a formula, worked example, milestone brief, and quality and cost guardrails.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/time-to-value","content":"# Time-to-Value (TTV): definition, formula, and AI examples\n\nTime-to-Value (TTV) measures the elapsed time between a defined starting event and a useful business outcome. For an initial AI deployment, AI Agentship measures from the agreed kickoff to the first result verified by the workflow owner. Define the outcome before building and track quality, cost, and review effort alongside speed.\n\n## How do you calculate Time-to-Value?\n\nTTV = verified value timestamp minus agreed start timestamp. Use calendar hours or days consistently. The start might be a customer onboarding event or an implementation kickoff; name it explicitly so people know which interval is being measured. Comparing unlike starting points can make an unchanged process appear faster.\n\nFor a first AI workflow, agree the milestone with its owner before work starts. Record the deliverable, acceptance standard, baseline, intended use, and cost boundary. A connected tool or a completed demo is a technical milestone. It becomes a value milestone only when the agreed business benefit is demonstrated.\n\n## Worked example: the first accepted client report\n\nIllustrative example, not an AI Agentship customer result: an agency starts a reporting implementation on October 4. On October 10, the account owner accepts and uses a real client report that meets the agreed source and accuracy checks. The first-value TTV is 6 calendar days. The clock includes the time spent resolving access and reviewing the output.\n\nSuppose a comparable report previously required four hours of preparation and review, and the new report requires two and a half hours. That single observation supports the first milestone if the quality and cost checks also pass. It does not establish a sustained saving, monthly ROI, or the capacity to serve additional clients. Check repeated reporting cycles before making those claims.\n\n## A first-value brief your team can use\n\nWrite these fields before configuring the agent: workflow and owner; who receives the result; start event and timestamp; current baseline; first-value event; acceptance evidence; permitted sources and tools; reviewer; cost limit; and the next scheduled use. Keep this brief beside the task and its output so a reviewer can inspect what was actually agreed.\n\nFor a research workflow, the first-value event could be a sourced brief used in a real client decision with less total research and checking effort than comparable work. For onboarding, it could be a verified client setup that enables the first agreed service activity. Choose the event that matters to that team rather than reusing a generic activation label.\n\n## Keep delays, failures, and review in the measurement\n\nDo not restart the main clock when data or permissions become available. Record blocked time separately so its cause can be fixed. Keep unfinished and cancelled implementations visible. A median drawn only from completed successes can look better while more customers never reach value.\n\nCompare similar workflows and report both completion time and the share reaching value within the agreed target. Alongside TTV, track material errors, review and rework hours, and total delivery cost including AI usage and allocated software. A faster result is not an improvement if it transfers more risk or unpaid correction to the team.\n\n## How does an FDO work toward shorter TTV?\n\nA Forward-Deployed Operator connects business discovery with implementation and adoption. The FDO helps define the outcome, prepare context, resolve access, configure agent tasks, and make review and ownership explicit. This gives the team a practical way to address the blockers between kickoff and value.\n\nTTV is the first milestone, not the end of operations. The team still needs a runbook, exception handling, a named maintainer, and evidence that the result can be repeated. Timing depends on scope and readiness; neither a fixed deadline nor a percentage reduction is implied.\n\n## Implementation checklist\n- Name the start event and do not reset it.\n- Agree one valuable outcome and its owner.\n- Record the baseline and acceptance evidence.\n- Include blocked time, review, rework, and total cost.\n- Keep incomplete deployments visible.\n- Verify repeated use after the first milestone.\n\n## Sources and further reading\n- [Gainsight: customer onboarding metrics and TTV](https://www.gainsight.com/glossary/entry/customer-onboarding-metrics/)\n- [TSIA: forward-deployed engineering and operating outcomes](https://www.tsia.com/blog/forward-deployed-engineering-ai-era)\n\n## Keep learning\n- [What is a Forward-Deployed Operator?](https://www.aiagentship.com/guides/forward-deployed-operator)\n- [AI implementation roadmap: from pilot to verified value](https://www.aiagentship.com/guides/ai-implementation-roadmap)\n- [AI reporting for agencies: automate preparation, keep review](https://www.aiagentship.com/guides/ai-reporting)\n\nSource: https://www.aiagentship.com/guides/time-to-value\n\nPublished: 2026-10-18\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/forward-deployed-operator-vs-engineer","title":"Forward-Deployed Operator vs Engineer: FDO and FDE compared | AI Agentship","description":"Compare FDO and FDE responsibilities, technical depth, operating ownership, and Time-to-Value. Choose the capabilities your AI implementation needs.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/forward-deployed-operator-vs-engineer","content":"# Forward-Deployed Operator vs Engineer: FDO and FDE compared\n\nForward-Deployed Engineers usually emphasize building technical solutions inside a customer environment. At AI Agentship, Forward-Deployed Operators emphasize connecting the business workflow, systems, people, and adoption around a verified outcome. The roles overlap, titles vary, and complex implementations may need both engineering depth and operating ownership.\n\n## What does each role own?\n\nAn FDE may build production software, integrations, data pipelines, and the architecture required for a deployment. A useful evaluation asks whether the person can implement, test, and maintain the technical system the engagement requires. Customer collaboration and business outcomes are part of forward-deployed engineering too.\n\nAn FDO maps how the work actually happens, agrees the first valuable result, coordinates knowledge and tool access, configures the workflow, and helps the team use it. The FDO can write code, use low-code tools, or partner with engineers. Operating judgment does not remove the need for technical depth where the system demands it.\n\n## Why Time-to-Value matters to both roles\n\nCode deployed is not the same as a business outcome accepted. Track the path from the agreed kickoff to the first verified result, including the time spent resolving unclear requirements, access, review, and adoption. Engineering and operating work can each remove different blockers on that path.\n\nFor an agency reporting workflow, an engineer might build a reliable data connector and a tested processing service. An operator might define the report standard, source owners, review queue, account-team handoff, and first-value evidence. Assign these responsibilities explicitly even when one person covers both roles.\n\n## Choose capabilities before choosing the title\n\nStart with the work. If the problem requires custom infrastructure, secure integrations, or production code, identify who supplies and supports that engineering. If the bottleneck is unclear ownership, scattered knowledge, repeated handoffs, or low adoption, identify who can redesign and run that workflow with the team.\n\nUse a short responsibility brief: outcome owner; technical owner; source owner; reviewer; deployment approver; and runbook maintainer. One person can cover several responsibilities, but none should disappear between a vendor, an engineer, and the customer team.\n\n## What should you ask before an engagement?\n\nAsk for the scope, required access, acceptance tests, first-value milestone, and handover responsibilities. Ask how missing data, rejected outputs, and unavailable tools are handled. A prototype can demonstrate an approach, but it does not prove the reliability or economics of your live workflow.\n\nThe FDO title is emerging rather than a universal professional standard. Judge the actual responsibilities and evidence. AI Agentship uses the term for the person connecting business understanding, hands-on implementation, and operational ownership; the agreed engagement determines how much ongoing operation is included.\n\n## Implementation checklist\n- Define the outcome and technical constraints.\n- Assign engineering and operating responsibilities.\n- Name the reviewer and adoption owner.\n- Agree first-value evidence and total cost boundaries.\n- Document support, handover, and ongoing ownership.\n\n## Sources and further reading\n- [TSIA: FDE roles, service pods, and operating models](https://www.tsia.com/blog/forward-deployed-engineering-ai-era)\n\n## Keep learning\n- [What is a Forward-Deployed Operator?](https://www.aiagentship.com/guides/forward-deployed-operator)\n- [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\n- [AI implementation roadmap: from pilot to verified value](https://www.aiagentship.com/guides/ai-implementation-roadmap)\n\nSource: https://www.aiagentship.com/guides/forward-deployed-operator-vs-engineer\n\nPublished: 2026-10-18\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/ai-implementation-roadmap","title":"AI implementation roadmap: from pilot to verified value | AI Agentship","description":"Plan a scoped AI implementation with a first-value brief, readiness checks, representative tests, adoption, and a documented handover.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/ai-implementation-roadmap","content":"# AI implementation roadmap: from pilot to verified value\n\nAn AI implementation roadmap connects a business outcome to the knowledge, tools, agent tasks, evaluation, and adoption needed to deliver it. Start with one real workflow and an agreed first-value milestone. Expand only after the owner accepts the result and the team can repeat it within quality, cost, and permission boundaries.\n\n## 1. Select a workflow with a measurable result\n\nPick work the team already performs and can inspect: a recurring client report, an onboarding brief, or a research update. Name the owner, current inputs, expected output, and intended user. A request to transform the entire business is too broad to test as a first deployment.\n\nWrite the baseline before the build: preparation time, review and rework effort, turnaround, material errors, and current delivery cost. Agree what the first useful outcome would demonstrate. This becomes the value brief for the project, not a guarantee that AI is the best solution.\n\n## 2. Resolve readiness and access\n\nList the sources, tools, permissions, decisions, and people required. For each dependency record an owner, the current blocker, and what must be true before testing live work. Start with approved read-only access where possible and configure client boundaries explicitly.\n\nKeep the Time-to-Value clock anchored to the agreed kickoff while recording blocked time separately. If a source cannot be obtained, either change the scope transparently or stop. Quietly replacing missing business evidence with model-generated content is not a readiness solution.\n\n## 3. Build the smallest useful workflow and test it\n\nSeparate deterministic steps, such as arithmetic and required-field checks, from AI tasks such as extracting or drafting. Define input and output formats, permitted tools, approval boundaries, and what happens when a step fails. Keep the draft and supporting evidence together.\n\nUse representative tasks and failure cases: missing files, stale figures, contradictory sources, invalid access, and an output the reviewer rejects. Record the expected result before the test. A smooth happy-path demonstration does not show that the workflow is ready for everyday work.\n\n## 4. Verify value with the responsible team\n\nThe exit gate is an agreed result used in a real workflow, with evidence that its acceptance and benefit conditions are met. Record the acceptance timestamp, reviewer, output, source versions, total effort, and usage cost. Compare similar work rather than a simple task with a complex baseline.\n\nAn FDO helps connect the technical build to this operating gate. If the output is unusable or review costs erase the benefit, the project has learned something but has not met the value milestone. Revise the workflow, scope, or approach rather than counting deployment itself as success.\n\n## 5. Hand over, observe, and decide whether to expand\n\nA handover package should explain how to start and stop the workflow, inspect sources, approve an output, handle an exception, and recover from a failed connection. Name the maintainer and reviewer, record the supported scope, and make access removal part of the operating procedure.\n\nObserve repeated use before adding more work. Review quality, latency, cost per accepted output, and the effort required from the team. The roadmap is a sequence of evidence gates rather than a fixed number of days; timing and support depend on the implementation.\n\n## Implementation checklist\n- Write the outcome and baseline.\n- Assign owners for data, access, review, and adoption.\n- Build only the connections the task requires.\n- Test normal work and failures.\n- Record the first verified result.\n- Hand over and evaluate repeated use before expanding.\n\n## Sources and further reading\n- [TSIA: design, activation, realized outcomes, and ongoing evolution](https://www.tsia.com/blog/forward-deployed-engineering-ai-era)\n- [IBM: agentic workflows and traditional automation](https://www.ibm.com/think/topics/agentic-workflows)\n\n## Keep learning\n- [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\n- [AI workflow automation: build a useful agentic workflow](https://www.aiagentship.com/guides/ai-workflow-automation)\n- [What makes a workspace ready for AI agents?](https://www.aiagentship.com/guides/agent-ready-workspace)\n\nSource: https://www.aiagentship.com/guides/ai-implementation-roadmap\n\nPublished: 2026-10-18\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/ai-workflow-automation","title":"AI workflow automation: build a useful agentic workflow | AI Agentship","description":"Choose between rules and AI agents, map a workflow, set tool permissions, test failure paths, and measure Time-to-Value with human review.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/ai-workflow-automation","content":"# AI workflow automation: build a useful agentic workflow\n\nAI workflow automation uses models for tasks such as interpreting information, extracting fields, or drafting within a business process. An agentic workflow can also choose steps or tools within defined boundaries. Use deterministic automation for predictable rules and calculations, and retain explicit ownership, review, and exception handling around AI decisions.\n\n## When should you use rules, AI, or an agent?\n\nUse rules when the required behavior is known: validate a date, sum accepted figures, route a form by a fixed category, or check that a required field exists. Use a model when the task involves language or ambiguous information that fixed rules cannot handle well. Neither choice removes the need for testing.\n\nAn agent adds flexibility when the next permitted step depends on what it finds. That flexibility introduces more operating cases to inspect. A fixed sequence with one model call may be sufficient; multiple agents are not a prerequisite for a useful workflow.\n\n## Map the workflow before connecting tools\n\nFor each step record: trigger, input, source owner, transformation, output, permitted action, reviewer, and failure route. Keep human decisions visible alongside automated steps. If nobody can explain who accepts the output, the workflow is not ready to operate.\n\nExample design: an onboarding form passes required-field checks; an agent drafts a setup brief from approved client information; an operator verifies missing details; and a person approves the handoff. The draft does not authorize the agent to create accounts, send messages, or change customer records.\n\n## Give tools narrow responsibilities\n\nConnect only the sources and actions needed by the workflow through supported APIs or MCP interfaces. Apply access controls in the connected systems and runtime. Written instructions in a task file are not a substitute for permission enforcement.\n\nDefine timeouts, retry limits, duplicate handling, and a human fallback. If a tool is unavailable, preserve the task state and show what remains incomplete. Avoid hidden retries that create repeated writes or turn a low-cost task into an expensive loop.\n\n## Test accepted work, not just successful tool calls\n\nTest a normal case, incomplete input, conflicting evidence, access denial, and a rejected draft. Inspect the final artifact and action record. A successful API response only confirms a technical step; it does not establish that the team received a useful result.\n\nAn FDO uses Time-to-Value (TTV) to connect the implementation to its first verified business outcome. Track total delivery cost and human review effort as well. Retest after changing the model, knowledge, tools, or instructions, and expand only when repeated work meets the standard.\n\n## Implementation checklist\n- Choose rules for predictable behavior.\n- Define the workflow record and acceptance owner.\n- Give agents only the tools the task needs.\n- Set retry and exception boundaries.\n- Test incomplete inputs and rejected outputs.\n- Verify business value and repeated use.\n\n## Sources and further reading\n- [IBM: what agentic workflows are and how they operate](https://www.ibm.com/think/topics/agentic-workflows)\n\n## Keep learning\n- [AI implementation roadmap: from pilot to verified value](https://www.aiagentship.com/guides/ai-implementation-roadmap)\n- [AI reporting for agencies: automate preparation, keep review](https://www.aiagentship.com/guides/ai-reporting)\n- [AI knowledge base: build a company brain agents can use](https://www.aiagentship.com/guides/ai-knowledge-base)\n\nSource: https://www.aiagentship.com/guides/ai-workflow-automation\n\nPublished: 2026-10-18\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/ai-reporting","title":"AI reporting for agencies: automate preparation, keep review | AI Agentship","description":"Build a client-reporting workflow with trusted data, metric definitions, agent drafts, human approval, and a measurable first-value milestone.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/ai-reporting","content":"# AI reporting for agencies: automate preparation, keep review\n\nAI reporting combines reliable data preparation with model-assisted summaries, explanations, and report drafts. For agencies and professional firms, a useful system keeps metric definitions, sources, client context, and human approval together. The goal is an accepted report that supports client work, not simply a document generated faster.\n\n## Define the report the client actually needs\n\nStart with one recurring report and the decision it supports. Name the account owner, reporting period, required measures, source systems, and approval standard. Keep data collection, calculations, narrative drafting, and client delivery as separate responsibilities.\n\nA report contract can use these fields: measure name; business definition; source and source owner; date range and time zone; calculation rule; known limitation; narrative question; reviewer; and delivery destination. This makes the report reviewable before AI writes its commentary.\n\n## Connect sources and prepare an evidence-backed draft\n\nCollect approved data and calculate defined metrics with deterministic queries or code. Supply the model with the results, relevant client context, and the report format. Ask it to distinguish observed changes from possible explanations and to flag missing information.\n\nDo not infer the cause of a performance change from correlation alone. If a channel shows lower conversions, the draft should point to the observed figures and identify what needs investigation. An agent should not invent an explanation to fill an empty section.\n\n## Make review part of the workflow\n\nThe reviewer checks figures, time periods, source freshness, client identity, claims, and recommendations. Preserve the source snapshot or query record used for the draft. Keep rejected versions and corrections available so recurring problems can be fixed at their source.\n\nA suggested output record includes draft link, source references, unresolved questions, review state, reviewer, acceptance timestamp, and delivery approval. A completed draft does not automatically authorize a client email or an update to a business record.\n\n## Measure the first useful report and subsequent cycles\n\nAgree a first-value milestone before implementation: a real report is accepted and used, meets its standard, and demonstrates the intended benefit against comparable baseline work. Measure Time-to-Value from the agreed kickoff to that verified event. A sample dashboard or fabricated dataset is useful for testing but does not satisfy a live reporting milestone.\n\nFor subsequent cycles, compare preparation, review and rework, turnaround, and total cost per accepted report. Include connector costs, model usage, and human effort. A faster draft that increases checking time may not improve delivery economics. Use representative reporting periods before claiming a sustained improvement.\n\n## Implementation checklist\n- Name the report, decision, and owner.\n- Write metric definitions and source requirements.\n- Calculate figures outside the narrative model.\n- Keep evidence and unresolved questions beside the draft.\n- Require approval before client delivery.\n- Measure first value and repeated accepted reports.\n\n## Sources and further reading\n- [Supermetrics: AI-powered marketing reporting for agencies](https://supermetrics.com/blog/ai-powered-marketing-reporting-agencies)\n- [Gainsight: defining Time-to-Value](https://www.gainsight.com/glossary/entry/customer-onboarding-metrics/)\n\n## Keep learning\n- [Time-to-Value (TTV): definition, formula, and AI examples](https://www.aiagentship.com/guides/time-to-value)\n- [AI workflow automation: build a useful agentic workflow](https://www.aiagentship.com/guides/ai-workflow-automation)\n- [AI knowledge base: build a company brain agents can use](https://www.aiagentship.com/guides/ai-knowledge-base)\n\nSource: https://www.aiagentship.com/guides/ai-reporting\n\nPublished: 2026-10-18\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/guides/ai-knowledge-base","title":"AI knowledge base: build a company brain agents can use | AI Agentship","description":"Organize business knowledge for AI with source ownership, retrieval, permissions, evidence, and evaluation tied to a useful workflow.","modifiedAt":"2026-10-18","url":"https://www.aiagentship.com/guides/ai-knowledge-base","content":"# AI knowledge base: build a company brain agents can use\n\nAn AI knowledge base makes approved business information retrievable by people and AI systems. A useful company brain includes source ownership, dates, permissions, definitions, and reviewed examples. Retrieval can ground a response in company content, but it does not guarantee accuracy, current information, or permission enforcement by itself.\n\n## Start with a workflow and its real questions\n\nChoose the work the knowledge must support: preparing a client brief, answering a process question, or drafting a report. List the questions a competent team member would need to answer and the approved sources behind each answer. Uploading every document does not define a useful knowledge system.\n\nA starter record can contain title, source URL or location, owner, approved use, client boundary, version, last review date, and expiry rule. Keep methods, metric definitions, policies, and reviewed examples distinguishable so the system can use the right kind of evidence.\n\n## What retrieval-augmented generation does\n\nRetrieval-augmented generation, or RAG, retrieves relevant material and supplies it to a model as context for a response. Its usefulness depends on whether the correct information is retrieved and whether the response uses that evidence appropriately. A vector database is one possible component, not the whole business operating system.\n\nKeep source references visible to the person checking the answer. Test questions that use different wording from the documents and questions that need information from more than one source. More retrieved text is not automatically better context.\n\n## Make permissions and missing evidence explicit\n\nApply access boundaries before retrieval and output. A shared prompt telling an agent not to expose another client is not sufficient isolation. Configure controls in the source systems, retrieval service, workspace, and agent runtime used by the implementation.\n\nDefine what happens when a document is stale, sources disagree, or the user lacks access. A useful response can say that evidence is missing and route the question to its owner. The system should not invent a policy or silently treat an old example as a current rule.\n\n## Evaluate the company brain against accepted work\n\nCreate a small, representative question set with expected sources and reviewer notes. Include an answerable question, an ambiguous question, a missing answer, a stale source, and a prohibited cross-client request. Record source relevance, unsupported claims, correct refusal or escalation, and review effort.\n\nConnect the knowledge base to one useful workflow before expanding. An FDO organizes the knowledge, access, instructions, and review around its first valuable result. Measure Time-to-Value to that verified event, then check whether knowledge maintenance and repeated use remain sustainable.\n\n## Implementation checklist\n- Name the workflow and its knowledge questions.\n- Record source ownership, dates, and approved use.\n- Configure access outside the prompt.\n- Return evidence with the answer.\n- Test stale, missing, and prohibited information.\n- Measure a verified workflow result and ongoing maintenance effort.\n\n## Sources and further reading\n- [Microsoft Learn: retrieval-augmented generation and its challenges](https://learn.microsoft.com/en-us/azure/search/retrieval-augmented-generation-overview)\n\n## Keep learning\n- [What makes a workspace ready for AI agents?](https://www.aiagentship.com/guides/agent-ready-workspace)\n- [AI implementation roadmap: from pilot to verified value](https://www.aiagentship.com/guides/ai-implementation-roadmap)\n- [AI reporting for agencies: automate preparation, keep review](https://www.aiagentship.com/guides/ai-reporting)\n\nSource: https://www.aiagentship.com/guides/ai-knowledge-base\n\nPublished: 2026-10-18\nUpdated: 2026-10-18\n\nExplore plans: https://www.aiagentship.com/#pricing\n","language":"en"},{"path":"/agents","title":"Agent Access & WebMCP Tools | AI Agentship","description":"Discover public AI Agentship content, inspect WebMCP tools, and navigate offers and guides from a compatible browser agent.","url":"https://www.aiagentship.com/agents","content":"# AI Agentship — agent access guide\n\nBuild your human + AI workspace. Forward-Deployed Operators connect knowledge, tools, and review around Time-to-Value (TTV). Start free.\n\n## Discover\n- Canonical website: https://www.aiagentship.com/\n- Human-readable agent guide: https://www.aiagentship.com/agents\n- Short summary: https://www.aiagentship.com/llms.txt\n- Full public content: https://www.aiagentship.com/llms-full.txt\n- Content index: https://www.aiagentship.com/ai-index.json\n- Structured data: https://www.aiagentship.com/schema.json\n- Tool manifest: https://www.aiagentship.com/.well-known/mcp.json\n\n## WebMCP browser tools\nOpen an HTML page in a compatible browser or bridge. Tools are registered on document.modelContext; browser support is provided by the MCP-B runtime when needed. Discover tools with getTools() and call executeTool(descriptor, inputObject). This is browser-session tooling, not a remote HTTP MCP server.\n\n- get-site-overview: identity, capabilities, plans, and destinations.\n- get-plans: compare free workspace, $230 one-time Pro, and $500/month support.\n- get-faqs: retrieve public answers, optionally filtered by query.\n- search-site: search guides, FAQs, plans, and capabilities.\n- find-site-section: return a public section URL.\n- navigate-site: visibly navigate to a listed section or guide index.\n- get-next-step: return an approved workspace, Pro, support, consultation, implementation, or partnership URL.\n- activate-site-action: reveal and focus the matching human CTA; return its destination.\n- get-service-cards, reveal-free-fdo-workspace, show-organization-faq, reveal-implementation-support: public tools for service cards, the free workspace, FAQs, and paid implementation support.\n\n## Boundaries\nTools inspect public data or update page navigation. They do not complete purchases, subscribe, send messages, submit forms, or book appointments. Checkout and booking happen on Whop or Calendly. Confirm a consequential action with the user there. No credential, email address, or personal data is required by these tools.\n\n## Content for retrieval\nUse /index.md or /llms-full.txt for explicit markdown resources. Public HTML pages also support Accept: text/markdown. Machine-readable guides are informational aids, not authorization to change business systems.\n\nUpdated: 2026-10-19\n","language":"en"}],"resources":{"agents":"https://www.aiagentship.com/agents.txt","summary":"https://www.aiagentship.com/llms.txt","full":"https://www.aiagentship.com/llms-full.txt","tools":"https://www.aiagentship.com/.well-known/mcp.json"}}