Now
What Audora is,
and where it is going.
This page is a live view of what is shipped, what is being built, and what is further out. We update it as things change. No vague timelines. No marketing fluff.
The Audora bot joins any Zoom meeting via link, transcribes in real time with full speaker labeling, and processes the call immediately when the session ends. No host setup or special permissions required.
Available on all plans.
Joins Google Meet sessions as an external participant via calendar event or direct link. Works with personal Google accounts and Google Workspace. Speaker identification and real-time transcription included.
Available on all plans.
Audora joins Teams meetings as an external participant - no admin configuration needed on your organization's side. Full transcription and speaker labeling identical to Zoom and Meet.
Available on Studio and Agency plans.
Every call is transcribed in real time with each speaker identified and labeled separately. The transcript is stored in your Audora dashboard and used as the source of truth for all six generated outputs. Transcripts are searchable and available immediately after the call ends.
The recording is deleted within 72 hours of transcription. Only the transcript and outputs are retained.
From every transcribed call, Audora generates: a full transcript, a client brief, a requirements document, a product requirements document (PRD), a task breakdown with time estimates, and a statement of work (SOW). All six are available in the dashboard within 60 seconds of the call ending.
All outputs available on all plans.
Audora writes the PRD and task breakdown to your project repo as a structured file. Opening Cursor on the project loads the full spec as working context immediately - no copy-pasting, no prompt engineering to get it started.
Available on all plans.
Audora generates a Lovable-ready project link from your PRD, optimized for Lovable's prompt structure. One click lands you inside Lovable with the full specification pre-loaded as the initial prompt.
Available on all plans.
Identical mechanism to Lovable - a pre-loaded Bolt project link generated from your spec. One click to open, full requirements already there as the starting prompt. Useful when a project calls for Bolt's full-stack generation approach.
Available on all plans.
Audora creates a new Linear project from the call and populates it with issues drawn directly from the task breakdown. Each task becomes a properly scoped issue with a description pulled from the requirements document. Your sprint board is ready before you close the meeting window.
Available on Studio and Agency plans.
Audora creates a new Notion page in your workspace containing the complete project package - PRD, requirements, task checklist, and SOW - organized in a structured, shareable layout. Useful for teams managing projects in Notion or for sharing a client-facing document.
Available on Studio and Agency plans.
These are the things we are actively building next. No dates - we ship when it is right, not when a deadline says so. If something on this list is particularly important to you, tell us - it affects what we prioritize.
Replit push
Audora will create a new Replit project with your spec pre-loaded as the opening AI prompt, following the same mechanism as Lovable and Bolt. Particularly useful for builders who work in cloud-based environments or who hand off builds to collaborators without a local dev setup. Will be available on all plans on launch.
Claude Code push
Audora will inject the PRD as the opening system context for a new Claude Code terminal session, with the task list written to the project directory for reference. When you open Claude Code, the full specification is already the working context - no additional prompting needed to get it oriented on the project. Available on all plans.
Custom output templates
Right now Audora generates outputs in a standard format. Custom templates will let you define exactly how each output looks - the structure of your PRDs, the format of your task breakdowns, the language of your SOWs. Useful for agencies that have established document formats their clients expect, or for builders who want outputs pre-formatted for specific tools or workflows. Available on Studio and Agency plans.
Client profiles per project
The ability to create a persistent profile for each client - their name, company, preferences, ongoing project context, and communication style. Once a client profile exists, Audora uses it to inform every output generated from calls with that client. The SOW will reference the right project name, the brief will match their communication preferences, the requirements will carry context from previous calls. The product gets smarter the more you use it for a given client.
Call history and search
A searchable archive of every call processed through Audora - transcripts, outputs, and metadata. Find any call by client name, keyword, date, or phrase that appeared in the transcript. Useful for reviewing what was discussed months ago, pulling an old SOW, or tracking how a project has evolved across multiple calls. Available on all plans; search depth will scale with plan tier.
Slack notifications
When a call is processed, Audora will post a summary to a Slack channel of your choice - call participant names, the key decisions from the call, and a link to the full outputs in the dashboard. Useful for team awareness on Studio and Agency plans where multiple people are running calls. No Slack required to use Audora - this is an optional add-on for teams already in Slack.
Team collaboration features
Studio and Agency plans already support multiple seats. What is coming is deeper collaboration - shared call libraries across team members, the ability to assign outputs to specific team members for review, comment threads on generated documents, and role-based visibility controls. Built for small agencies where multiple people are involved in the same client relationship.
More meeting platform support
We currently cover Zoom, Google Meet, and Microsoft Teams - the three platforms that account for the overwhelming majority of professional calls. We are evaluating additional platforms based on what our users actually use. If there is a specific platform you need that is not on this list, let us know - it directly informs what we build next.
Mobile app
A mobile companion app for reviewing call outputs, checking your dashboard, and managing your account on the go. The core product - the bot joining calls and generating specs - will remain desktop-first by design, since that is where builders work. The mobile app is for the moments when you are away from your desk and want to review what came out of a call or share an output with a client.
These are things we intend to build but are not actively working on yet. They are on the roadmap because they clearly make sense for where Audora is going - but we are being deliberate about what we build and in what order. We would rather ship ten things properly than twenty things poorly.
Zapier and webhook integrations
A general-purpose automation layer that lets you connect Audora outputs to any tool through Zapier or a custom webhook. When a call is processed, you could automatically trigger a CRM update, send an email, create a row in a spreadsheet, or post to any endpoint. This unlocks Audora for workflows we have not anticipated.
GitHub push
Audora will create a new GitHub repository from the call, pre-populated with the PRD, task breakdown, and a basic project structure. This goes one step beyond the Cursor integration - instead of writing a spec file into an existing project, it initializes the project itself from the call output.
Figma push
From the requirements document, Audora will generate a Figma FigJam board with the key user flows, feature list, and product structure mapped out visually. Useful for builders who start a project with a design conversation before writing any code - gives the design phase a starting structure without manually translating the PRD.
Voice upload for async calls
The ability to upload an audio or video file of a call that Audora was not present for - a recorded Loom, a downloaded call recording, a voice memo - and run it through the same processing pipeline to get the full output package. Covers the cases where the bot could not join or where the conversation happened outside a scheduled meeting.
Client-facing portal
A shareable link that lets your client view the outputs from their own call - the brief, the requirements, the SOW - without needing an Audora account. The client can review, comment on, and sign off on the scope directly from the portal. Turns the post-call package into a lightweight project approval workflow.
CRM integrations
Direct integrations with CRM platforms so that call outputs - client name, project details, SOW value, agreed scope - flow into the relevant contact or deal record automatically. Targets agencies that manage a significant volume of client relationships and need Audora's outputs to live alongside their existing sales and client management records.
Custom branding on outputs
The ability to apply your agency's logo, colors, and typography to generated SOWs, briefs, and client-facing documents - so the output looks like it came from your agency, not from a third-party tool. Particularly relevant once client-facing portals are live, and for agencies that send generated SOWs directly to clients as formal documents.