Frequently asked questions
Find the confirmed prices, current prelaunch status, and details still awaiting approval.
What exactly is Grunt?
Grunt is a prelaunch workflow product for recurring digital work, with configurable steps and human review. The public examples illustrate the product direction; they do not establish live customer availability.
Do I need to know how to code?
The implemented editor uses configurable workflow steps. Actual setup depends on published steps, supported connections, and permissions; setup time and customer onboarding have not been validated.
Can I try it before choosing a plan?
The homepage has an interactive preview with sample data and simulated connections. It does not create a workspace, connect real accounts, or perform work, and it is not a trial subscription.
Is Grunt available to use?
As of October 26, 2026, Grunt remains prelaunch. Live service is paused, and live provider connections and outcomes remain unverified. You can explore the homepage simulation and read the confirmed prices while availability is pending.
How do I invite my team?
Organization membership and permissions are implemented. Customer availability, user allowances, and plan-specific collaboration entitlements remain pending.
Do you charge per user?
User allowances and any per-user fees remain unapproved. The confirmed subscription prices are Pro $99/month USD, Team $500/month USD, and negotiated Enterprise.
Which plans are confirmed?
Pro is $99/month USD, Team is $500/month USD, and Enterprise pricing is negotiated. There is no Solo plan. Included Work, plan-specific features, and other commercial terms remain pending.
What are concurrent executions?
Concurrent executions are workflow runs active at the same time. Plan-specific concurrency limits have not been approved; no unlimited execution capacity is promised.
What is a work unit?
Work is Grunt’s usage-accounting unit, separate from subscription payments and supplier costs. A Work allowance is not a fixed number of workflow runs. Included amounts, rates, and overage terms remain to be finalized.
Do you offer nonprofit or startup discounts?
Startup and nonprofit programs are under consideration. No discount amount, eligibility criteria, duration, or program terms have been approved; the program pages show pending status.
What happens when there is not enough work left?
The implementation supports usage reservations and spending limits. Commercial Work allowances and overage handling remain pending; this does not promise that an admitted run always finishes.
Do revisions use work?
A revision may involve additional processing. Customer rates and charging terms for revisions have not been finalized.
What about refunds, taxes, and plan changes?
Refund entitlements, tax treatment, renewal and cancellation terms, and plan-change conditions remain unapproved. The pricing page publishes the confirmed monthly prices without inventing those terms.
How do I get help?
A verified public support contact and response commitments have not been published. This FAQ and the pricing and legal pages record the current prelaunch status.
What happens if a connected tool is unavailable?
Behavior depends on the step and provider. An interrupted request may have an uncertain outcome, so a failed connection does not prove that nothing happened. Live recovery behavior remains to be accepted.
Where can I learn how Grunt works?
The homepage preview is a simulation. The workflows directory contains illustrative ideas, and the integrations directory contains research. Neither directory is an inventory of published runnable customer features.
Is priority support or an SLA included?
Support levels, onboarding commitments, and service-level agreements have not been approved for any plan.
How is my data handled?
Approved privacy disclosures and a Data Processing Addendum are pending. Processing locations, supplier terms, retention periods, and a verified privacy contact remain unresolved; the legal hub shows that status.
Can I control what a workflow can access?
The implementation checks workflow permissions and separate information-access rules. Source access, result access, and permitted destinations must be configured. Human review does not itself grant access to information.
Does Grunt get access to all my tools?
Connecting an account does not grant a workflow access to all its information. Supported steps also require current source and destination permissions. Provider availability and actual account setup remain separate requirements.
Where can I read your security documentation?
The security page in the legal hub is a pending-status notice. Approved security assurances, certifications, monitoring commitments, and a verified reporting contact have not been published.
What kinds of tasks can I hand over?
The intended launch workflows cover correspondence-to-project tasks, follow-ups, briefings, opportunity research, staff alerts, and reviewed replies. The six launch compositions remain unpublished, and live-provider acceptance is unverified. Directory examples are broader ideas, not available templates.
Can I review work before it goes anywhere?
Human review and separate preparation and delivery steps are implemented. Review applies to the specific proposal and its context; it is not blanket permission for later actions. Customer-ready workflows remain pending publication and live acceptance.
Do I have to approve every step?
Review requirements depend on the published step and intended action. A workflow cannot use an optional review setting to bypass a required permission or final-action review.
Which tools can Grunt connect to?
The integrations directory lists researched possibilities, not verified live connections. Intended launch paths involve Basecamp, Gmail or Microsoft mail, and managed SMS, WhatsApp, or Telegram channels. Exact operations, account approvals, publication, and live-provider acceptance must be confirmed separately.
Do I need to connect every account at once?
A workflow needs its specific supported connections and permissions. Managed messaging can also require sender registration, recipient consent, and provider approval; setup time, number charges, and message allowances remain unconfirmed.
Where can I read the legal documents?
The legal hub preserves the privacy, terms, acceptable-use, DPA, subprocessors, cookies, and security URLs. Each currently shows a pending-status notice rather than an approved agreement or policy.
Do you offer a Data Processing Addendum?
An approved Data Processing Addendum is not yet available. Processing roles, supplier terms, transfer safeguards, deletion, and audit obligations remain unresolved.
Do you support audit logs?
The implementation records operational and audit events, but customer audit-log access, exports, and plan entitlements have not been approved. SAML SSO and custom retention are not confirmed Enterprise offerings.
How do you handle data retention?
Customer retention, deletion, backup periods, and storage allowances remain unapproved. Implemented storage or cleanup controls do not establish a contractual retention period or an unlimited-storage offer.
Where can I find your subprocessors?
The subprocessors page currently shows pending status. Implemented provider adapters and regional endpoints do not establish supplier approval, exclusive US processing, or provider training and retention protections.
Verified support and legal contacts are pending publication.
Read the legal status