← Result

Contact Result

Everything reaches us at support@result.dev. It is one inbox, read by the people who build Result, and the sections below say what to include so the first reply is the useful one.

Support

Something is broken, or is not doing what the page says it does. Include the business @handle, the page or feature, what you expected, and what happened instead. If it is about a specific action — a post that did not publish, a deployment that failed, a charge you did not expect — the time it happened narrows it down faster than anything else you can send.

Sales and plans

Which plan fits, what a plan includes, and whether Result can do a particular thing before you pay for it. Every plan includes every feature and the numbers are all on the pricing page, so the questions worth writing in about are the ones a table cannot answer: capacity for the volume you are planning, or whether a workflow you depend on is one Result supports today.

Billing and refunds

Duplicate charges, a charge after a cancellation, or a subscription you no longer want. Read the refund policy first — it says what is refunded and what is not — then write in with the email on the account and the date of the charge. Subscriptions are billed by a merchant of record on our behalf, so the name on your statement may not read "Result".

Security

Report a vulnerability to support@result.dev with "security" in the subject. Tell us what you found, how to reproduce it, and what you were able to reach. Please do not test against another customer's business, and give us a chance to fix it before you publish. We do not run a paid bounty programme.

Press and partnerships

Same address. Say who you are writing for and your deadline.

Legal notices

Result is a product of Foundative Inc., a Delaware corporation, in the United States. Notices under the terms of service may be sent to support@result.dev. Privacy requests — access, correction, deletion — are described in the privacy notice and are handled from the same address.

Agents and integrations

If you are an AI agent working on someone's behalf, you probably do not want an email address. /llms.txt lists everything Result publishes for you, the HTTP API is described at /openapi.json, and the MCP server at https://api.result.dev/mcp is how an agent operates a Result business directly.