Name the job and how it could go wrong.
We agree on the task, the information it can use, and what a useful result looks like. We also decide what it must never do and when a person needs to review its work.
Answer common questions, sort requests, or prepare drafts for your team. We build and maintain the setup using information you approve. Before launch, we agree on the costs, review steps, and when a person must take over.
Choose one task, agree on the rules, and test a useful first version. We keep checking and improving it after launch.
We agree on the task, the information it can use, and what a useful result looks like. We also decide what it must never do and when a person needs to review its work.
We connect the approved tools and information, test the results, and set up a way for a person to review or take over.
We check the results, fix incorrect source information, and adjust the setup. Updates and provider changes are handled as agreed in your plan.
Good. It should solve a specific problem. We only include building blocks with an approved source, owner, action, and review boundary.
Website or internal answers grounded in the hours, services, policies, documents, and other sources your organization approves.
Replies, summaries, articles, messages, or follow-up drafts routed to the person or team responsible for approval.
Turn incoming documents, forms, notes, or messages into structured fields, summaries, tags, and next-step queues.
Classify routine requests, identify missing information, and send work to the right person without pretending every decision is automatic.
Bring updates from your approved tools into one summary. Your team can see what needs attention without opening each system.
Source limits, approval rules, blocked topics, logs, and a clear next step when the workflow is uncertain.
A practical workflow can save real work before anyone asks the system to make a sensitive decision or act without review.
Strong fit
People regularly answer the same question, summarize the same material, or move the same information between systems.
The workflow can create value before anyone trusts it to take an irreversible action.
The organization can identify who approves sensitive outputs, corrects source facts, and handles uncertain cases.
Do not automate this yet
A model cannot create a trustworthy operating fact from stale policies, contradictory records, or information no one owns.
Medical, legal, employment, credit, safety, or other consequential decisions need specialist controls beyond a general marketing promise.
A feature should remove a known task or improve a measured outcome. A broad transformation label is not a sufficient scope.
The agreement identifies what the system may read, produce, store, recommend, and do, plus the person responsible for review and exceptions.
AI work can be part of a Business plan. Your proposal names the task, usage limits, review rules, providers, and any extra costs.
Business
From $950
USD per month
Practical AI work can be included in the Business operating scope alongside the app, website, customer workflows, and ongoing support. The proposal names the actual job and limits.
Review Business pricingThese pages show the sources behind price, ownership, review, privacy, and provider boundaries.
Decision guide
Check the task, source, risk, and human owner before you build.
Operating model
See who handles changes, who owns what, and what happens if you leave.
Public policy
Read the public privacy policy and current subprocessor disclosure.
Straight answers about models, review, data, pricing, and measurement.
No. We build a setup for a specific task using information you approve, with clear rules and a person responsible for it. A model may be part of that workflow, but access to a general chat interface is not the product.
The model depends on the task, data, quality needs, latency, cost, and contractual constraints. Providers and models can change. The scope should describe the job and controls so the workflow is not defined by one model name.
Only when the signed scope explicitly permits that action and defines the source, guardrails, monitoring, and fallback. Human review is the safer default for sensitive or customer-facing output until the workflow has evidence that supports a narrower rule.
Data handling follows the signed customer agreement and Rehost's public privacy and subprocessor disclosures. The scope should name approved sources, access, retention, processors, logs, exports, and prohibited uses for the workflow.
You retain the content and data you provide. Under the public Terms, Rehost owns its service software, code, and designs unless a signed customer agreement grants a different license or handoff. The agreement should distinguish customer data, configured workflow behavior, vendor accounts, exports, and service software.
The public Business plan starts at $950 per month and can include defined AI work with the app, website, and operating service. Unusual model usage, data processing, compliance, or third-party costs are scoped before work begins.
The scope identifies observable signals for the job, such as review acceptance, response coverage, routing accuracy, time to resolution, or the number and type of exceptions. Rehost reports measured results without turning them into a universal guarantee.
Show us the task and the information your team uses. We’ll talk through what AI could handle and what should stay with a person.