The Ultimate Guide to Documenting Multi-Step Processes Across Different Tools (2026 Edition)

In the dynamic business landscape of 2026, most organizations rely on an interconnected ecosystem of software tools to function. From customer relationship management (CRM) platforms and enterprise resource planning (ERP) systems to project management software, communication applications, and specialized creative suites, the average employee navigates multiple interfaces daily. While each tool offers unique capabilities, the real challenge – and opportunity – lies in the multi-step processes that span these applications.

Consider the journey of a new client from initial lead in HubSpot to contract signing in DocuSign, project setup in Asana, and billing in QuickBooks. Or perhaps the complex monthly financial close involving data extraction from SAP, analysis in Excel, and reporting through a business intelligence dashboard. These are not isolated tasks; they are intricate sequences, often executed by different team members, across various platforms.

Without clear, accessible documentation, these multi-tool processes become fertile ground for inconsistencies, errors, and significant productivity bottlenecks. New hires struggle, experienced staff waste time recreating steps, and the organization suffers from a lack of operational clarity. This guide explores how to effectively document multi-step processes that crisscross different tools, offering practical strategies, real-world examples, and the latest technological solutions to ensure your operations are resilient and efficient.

Why Document Multi-Tool Processes? The Unseen Costs of Operational Ambiguity

The immediate answer often centers on training new employees, which is undoubtedly critical. However, the benefits of well-documented multi-tool processes extend far beyond onboarding, impacting nearly every aspect of an organization's performance. Neglecting this documentation introduces a range of hidden costs and risks.

Reducing Errors and Ensuring Consistency

When a process moves from one application to another, say from a CRM to an invoicing system, there are numerous points where manual data transfer, re-entry, or interpretation can lead to errors. A misplaced digit, an incorrect field selection, or a forgotten step can result in delayed payments, customer dissatisfaction, or compliance issues. Clear Standard Operating Procedures (SOPs) act as guardrails, defining precise actions at each transfer point, significantly reducing the likelihood of human error.

For example, a marketing coordinator processing lead handoffs from HubSpot to Salesforce without a documented procedure might inconsistently categorize leads or miss a crucial follow-up flag. This could mean a lost sales opportunity, costing the company hundreds or even thousands of dollars in potential revenue. Documented SOPs for multi-tool operations ensure every marketing coordinator follows the exact same steps, maintaining data integrity and consistent lead quality.

Accelerating Onboarding and Training

Imagine a new Sales Development Representative (SDR) joining a team. Their role might involve logging interactions in Salesforce, scheduling meetings in Outlook, tracking progress in Jira, and communicating internally via Slack. Without comprehensive guides, their initial weeks are spent asking colleagues for clarification, navigating systems blindly, and inevitably making mistakes.

Well-structured documentation for multi-step processes across different tools can reduce onboarding time by 25-30%. Instead of ad-hoc training sessions and constant interruptions, new hires can follow precise, visual guides, allowing them to become productive much faster. This not only saves the trainers' time but also minimizes the new hire's frustration and boosts their confidence.

Improving Efficiency and Productivity

Experienced employees often develop their own "workarounds" or preferred methods for navigating multi-tool processes. While effective for them, these individual approaches can lead to inconsistencies and make it difficult for others to assist or take over tasks. Documented processes identify the most efficient path, eliminating redundant steps and providing a standardized approach that benefits the entire team.

A well-documented content publishing workflow, spanning Figma for design, WordPress for content management, and Buffer for social media scheduling, can reduce the time spent on content deployment by 15-20%. This frees up content strategists and designers to focus on creative work rather than troubleshooting platform-specific issues.

Facilitating Knowledge Transfer and Business Continuity

When a key employee departs or is unavailable, their institutional knowledge often walks out the door with them. This is particularly problematic for complex, multi-tool processes they've mastered over years. Comprehensive SOPs ensure that critical operational knowledge is captured and retained within the organization, mitigating the risk of operational disruptions. This guarantees business continuity, even during personnel changes or emergencies.

Ensuring Compliance and Audit Readiness

Many industries operate under strict regulatory requirements, necessitating meticulous record-keeping and adherence to specific procedures. Multi-tool processes, especially those involving financial transactions, personal data, or sensitive information, must be executed precisely to meet compliance standards. Documented SOPs provide an auditable trail, demonstrating that established protocols were followed, protecting the company from potential penalties or legal issues.

For a financial analyst, documenting the quarterly reporting process that pulls data from multiple financial systems (e.g., SAP, Oracle Financials) into Excel for calculations and then into a reporting tool (e.g., Tableau) is crucial. It ensures every step, every data validation, and every sign-off is recorded, making the entire process transparent and ready for any internal or external audit.

The Unique Complexities of Cross-Application Workflows

Documenting a simple, single-tool process (like "how to reset your email password") is relatively straightforward. Documenting multi-step processes across different tools, however, introduces several layers of complexity:

1. Context Switching: Users constantly shift their mental models and interface familiarity between different applications. Each tool has its own UI/UX, terminology, and logic, making the overall process feel disjointed.
2. Data Hand-offs: Moving data from one system to another – whether through manual copy-pasting, CSV exports/imports, or API integrations – is a common point of failure. Documenting exactly which data fields map to which, and how to handle discrepancies, is critical.
3. Variations and Exceptions: Real-world processes are rarely linear. What happens if a payment fails in the invoicing system? How do you update the CRM? Documenting these branching paths and exception handling across different tools significantly increases the complexity.
4. Security and Permissions: Each tool has its own access control. A process might require specific permissions in one system that aren't available to all users who perform other steps in a different system. Documentation needs to address these access requirements.
5. Tool Updates: Software evolves. A UI change in Salesforce or an update to a Google Sheets function can invalidate a documented step. Multi-tool processes are more vulnerable to such changes, as a single update can break an entire sequence.
6. Human Interpretation: Even with clear instructions, the interpretation of a step can vary, especially when transitioning between tools. Visual aids become paramount to minimize ambiguity.

Traditional Methods: Why They Often Fall Short for Multi-Tool Processes

Historically, organizations have relied on several methods for process documentation. While some of these have their place, they often struggle with the intricacies of multi-tool workflows.

• Text-Based Documents (Word, Google Docs): While easy to create, these often become long, cumbersome, and difficult to follow. Describing visual actions like "click the third button from the left on the top navigation bar" is inefficient and prone to misinterpretation, especially when tool UIs change. For multi-tool processes, text alone struggles to convey the flow and context shifts.
• Static Screenshots in Manuals: Better than pure text, but still problematic. A series of screenshots can quickly become outdated. If a button moves or a field name changes in one of the applications, the entire sequence of screenshots may need redoing. The effort to maintain these for dynamic multi-tool environments is immense.
• Flowcharts and Diagrams: Excellent for illustrating the logic and decision points of a process, but they lack the granular, step-by-step visual detail needed for execution across different UIs. They show "what to do next," but not "how to do it" within a specific tool.
• Verbal Training and Shadowing: Highly effective for initial learning but unsustainable for long-term knowledge transfer. It's time-consuming, prone to inconsistencies, and doesn't create a persistent record. The moment the trainer or experienced employee isn't available, the knowledge gap reappears.
• Wikis and Internal Knowledge Bases: While useful for centralizing information, creating and maintaining detailed, step-by-step guides for complex multi-tool processes in a wiki can still be a labor-intensive manual effort, often suffering from the same update challenges as text documents and static screenshots.

The common thread among these traditional methods is the high manual effort required for creation and, crucially, for maintenance. In an environment where software updates are frequent, keeping multi-tool process documentation current using these methods quickly becomes an overwhelming, resource-intensive task.

Modern Approaches to Multi-Tool Process Documentation

The challenges of documenting multi-tool processes demand a more sophisticated, adaptable, and efficient approach. The best modern strategies combine clear textual instructions with strong visual guidance, automated capture, and intelligent organization.

1. The Power of Visual Documentation

Visuals are indispensable for multi-tool processes. A picture is indeed worth a thousand words, especially when dealing with software interfaces.

• Contextual Screenshots: Rather than generic full-screen grabs, focus on specific areas of the screen relevant to the step. Annotate these screenshots with arrows, highlights, and text overlays to draw attention to the precise elements a user needs to interact with.
• Short Video Clips: For particularly complex interactions or sequences of mouse clicks/keyboard entries, a short video clip can be more effective than a dozen static images. This is especially true when demonstrating the flow between different applications.
• Animated GIFs: Similar to video, GIFs are excellent for illustrating quick, repetitive actions or transitions without the overhead of full video playback.

2. AI-Powered Solutions for Automated Documentation (ProcessReel)

This is where the future of multi-tool process documentation truly shines. AI-driven tools have revolutionized the capture and generation of SOPs, significantly reducing manual effort and improving accuracy.

Tools like ProcessReel are specifically designed to address the pain points of documenting multi-step processes across different tools. Instead of manually taking screenshots, writing descriptions, and formatting documents, you simply perform the process as you normally would, while ProcessReel records your screen and narration.

How ProcessReel excels for multi-tool workflows:

• Automated Step Capture: ProcessReel intelligently detects your actions – clicks, keystrokes, navigation – across multiple applications. As you switch from Salesforce to Jira and then to Google Sheets, it continues to capture each step, distinguishing between applications.
• Narration Integration: Your verbal explanation of why you're performing a step or what to look for in the next tool is captured alongside the visual. AI transcribes this narration and integrates it into the step-by-step instructions.
• Smart Documentation Generation: From your recording, ProcessReel automatically generates a comprehensive, visually rich SOP. This includes annotated screenshots for each key action, detailed textual instructions (derived from your actions and narration), and often even a linked video of the recording.
• Easy Editing and Updates: Because the documentation is generated from a recording, making updates is vastly simpler. Re-record only the changed segment, and ProcessReel can update the relevant steps in the SOP, ensuring your multi-tool guides remain current with minimal effort.

This approach drastically cuts the time and resources traditionally required to create and maintain process documentation, making it feasible to keep even the most complex, cross-application workflows thoroughly documented. For more insights into this transformative approach, consider reading Master SOP Creation: How AI Transforms Standard Operating Procedures (2026 Guide).

Step-by-Step Guide: Documenting Multi-Tool Processes Effectively

Successfully documenting complex, multi-tool processes requires a structured approach. Here's a detailed methodology:

1. Identify the Process Scope and Purpose

Before you start recording or writing, clearly define what process you're documenting and why.

• Define Start and End Points: "The process begins when..." and "The process concludes when..." Be precise. For instance, "The client onboarding process starts when the sales team closes a deal in Salesforce and ends when the project is successfully set up in Asana and the initial invoice is sent from QuickBooks."
• Identify Key Stakeholders: Who performs this process? Who uses this documentation? Understanding your audience helps tailor the level of detail.
• List All Involved Tools: Make a comprehensive list of every application touched during the process. Examples: Salesforce, HubSpot, Jira, Asana, Google Sheets, Microsoft Excel, Slack, Microsoft Teams, DocuSign, QuickBooks, SAP, Workday, Figma, Adobe Photoshop, WordPress, Buffer.
• Outline the Objective: What is the desired outcome of this process? What problem does it solve, or what value does it create?

2. Map the Workflow (High-Level and Detailed)

This step involves visualizing the process before documenting individual actions.

• High-Level Flowchart: Use a basic flowchart or swimlane diagram to illustrate the sequence of major steps and the handoffs between different roles or tools. This provides a bird's-eye view.
  • Example: Lead Generation (HubSpot) -> Qualification (Salesforce) -> Proposal (DocuSign) -> Project Setup (Asana) -> Billing (QuickBooks).
• Detailed Step Breakdown: For each high-level step, identify the specific sub-steps and the tool(s) used for each. Think about decision points and potential error paths.
  • Example Sub-step (from "Project Setup"):
    • Receive "New Project" notification in Slack.
    • Log into Asana.
    • Create new project from "Client Onboarding" template.
    • Copy client details from Salesforce record into Asana project brief.
    • Assign tasks to team members.
    • Set project timeline.
    • Notify client via email (Gmail/Outlook) with project portal link.

3. Choose Your Documentation Method

Based on the complexity, frequency of updates, and resources available, select the most appropriate method.

• For simple, stable processes: Text with static screenshots might suffice.
• For complex, frequently updated, or multi-tool processes: ProcessReel (or similar AI-driven screen recording tools) is the recommended solution. It minimizes manual effort, ensures accuracy, and makes updates manageable. This is where AI truly transforms your documentation efforts.

4. Execute the Documentation (The "How-To" Part)

This is where you capture the actual steps.

• If using ProcessReel:

  1. Prepare Your Environment: Close unnecessary tabs and applications to minimize distractions in the recording. Ensure you have all necessary login credentials and test data ready.
  2. Start Recording with Narration: Launch ProcessReel. As you perform each step of the multi-tool process, clearly narrate your actions, the "why" behind them, and what to look for on the screen. For example, "Now I'm switching to Salesforce to find the client's ID. I'll navigate to the Accounts tab and use the global search bar."
  3. Perform the Process Naturally: Go through the entire multi-tool process from start to finish. Make sure to clearly show the transitions between different applications.
  4. Finish and Generate: Once complete, stop the recording. ProcessReel will automatically process your recording and narration, generating a detailed, visual SOP with screenshots, text descriptions, and a corresponding video.
  5. Review and Refine: Examine the generated SOP. Edit the text for clarity, add contextual notes, or make minor adjustments to screenshots if needed. This is much faster than creating from scratch.

• If using manual methods (less recommended for multi-tool processes):

  1. Perform Each Step: Execute the process slowly, one step at a time.
  2. Capture Visuals: Take precise screenshots for each significant action. For multi-tool processes, ensure each screenshot clearly shows the application it belongs to.
  3. Write Detailed Descriptions: For each screenshot, write clear, concise instructions. Explain what to click, what data to enter, and what the expected outcome is.
  4. Describe Tool Transitions: Explicitly state when the process moves from one application to another and what triggers that transition (e.g., "After clicking 'Save' in HubSpot, open Salesforce to update the lead status.").

5. Review and Refine

Never publish documentation without a thorough review.

• Self-Review: Read through the entire SOP, performing the steps yourself based only on the documentation. Does it make sense? Is anything missing? Are there ambiguities?
• Peer Review: Have someone unfamiliar with the process (ideally a new hire or someone who would actually use the SOP) test the documentation. Their feedback is invaluable for identifying unclear steps or missed information, especially for multi-tool transitions.
• Clarity and Conciseness: Remove jargon where possible. Use bullet points or numbered lists for readability. Ensure a consistent tone.
• Accuracy: Double-check all numbers, names, and button labels.

6. Maintain and Update

Documentation is a living asset. Set a schedule for regular reviews.

• Scheduled Reviews: Annually or semi-annually, review all critical SOPs to ensure they are still accurate.
• Triggered Updates: Update immediately if a software tool changes its interface, a process step changes, or an error is discovered. This is where the efficiency of ProcessReel for updates truly pays dividends.
• Centralized Storage: Store all documentation in an easily accessible knowledge base (e.g., a shared drive, internal wiki, or ProcessReel's cloud platform).

For help organizing your SOPs, explore resources like Master Operational Efficiency: The Best Free SOP Templates for Every Department in 2026 and The Definitive Guide to 10 Indispensable SOP Templates for Operations Teams in 2026.

Real-World Examples and Impact of Documented Multi-Tool Processes

Let's examine how documenting multi-tool processes with an AI tool like ProcessReel can generate tangible benefits.

Example 1: Client Onboarding for a SaaS Company

Process: Onboarding a new client from sales closure to service activation. Tools Involved: Salesforce (CRM), DocuSign (Contract Signing), Stripe (Payment Processing), Zendesk (Support Ticketing), internal custom application (Service Provisioning). Team Members: Sales Operations Specialist, Billing Clerk, Customer Success Manager, IT Operations Engineer.

The Challenge Before Documentation: Previously, this 12-step process was primarily handled through verbal instructions and ad-hoc emails. New Sales Operations Specialists took 4-6 weeks to become fully proficient. Manual data entry errors were common, particularly when transferring client details from Salesforce to the internal provisioning app, leading to service activation delays in 15% of new clients. Each delay cost the company approximately $200 in lost revenue and support time.

Solution with ProcessReel: The Sales Operations Lead used ProcessReel to record the entire client onboarding process. They performed the steps, narrating key data fields, security checks in DocuSign, and specific configurations within the custom provisioning application. ProcessReel automatically generated a comprehensive SOP for each step across the five tools.

Impact:

• Reduced Onboarding Time: New Sales Operations Specialists now become proficient in 2 weeks, a 60% reduction.
• Decreased Error Rate: Data entry errors for client provisioning dropped from 15% to less than 2%, saving the company an estimated $40,000 annually (20 new clients/month x 12 months x 13% error reduction x $200/incident).
• Improved Client Satisfaction: Faster, more accurate service activation led to a 10% increase in initial client satisfaction scores.
• Enhanced Team Collaboration: All teams now follow the same documented process, reducing back-and-forth communication by 30%.

Example 2: Monthly Financial Close for a Mid-Sized Manufacturing Firm

Process: Consolidating financial data and generating reports. Tools Involved: SAP (ERP), Microsoft Excel (Data Analysis and Adjustments), Tableau (Reporting Dashboard), SharePoint (Document Archiving). Team Members: Financial Analysts, Accountants, Financial Controller.

The Challenge Before Documentation: The monthly close, involving over 20 critical steps across three different departments, was highly manual and heavily reliant on a few senior financial analysts. If a key analyst was on leave, the close often faced delays. Data consistency issues between SAP exports and Excel manipulations were frequent, requiring rework and extending the close cycle by 2-3 days on average, costing the firm $5,000 per delayed day in opportunity costs and increased overtime.

Solution with ProcessReel: The Financial Controller recorded the entire monthly close process, detailing SAP data extraction parameters, specific Excel pivot table operations, data validation checks, Tableau dashboard updates, and final report archiving in SharePoint. ProcessReel created an accurate, visual guide.

Impact:

• Accelerated Close Cycle: The financial close now consistently completes 2 days faster, saving $10,000 per month or $120,000 annually.
• Reduced Error Rework: Data consistency errors decreased by 40%, freeing up 15 hours of analyst time each month.
• Improved Redundancy: Junior analysts can now confidently perform more steps of the close, ensuring business continuity even with staff changes.
• Enhanced Audit Readiness: Clear, step-by-step documentation simplifies internal and external audits.

Example 3: Software Release Deployment for a Tech Startup

Process: Deploying a new software version to production. Tools Involved: Jira (Project Management), GitHub (Code Repository), Jenkins (CI/CD Pipeline), AWS Console (Infrastructure Management), Slack (Notifications). Team Members: Software Developers, DevOps Engineers, Quality Assurance (QA) Analysts.

The Challenge Before Documentation: Release deployments were often inconsistent, depending on the individual DevOps engineer leading the effort. Misconfigurations in AWS, missed testing steps, or incorrect version tagging in GitHub led to post-deployment bugs in 10-12% of releases, requiring emergency rollbacks and hotfixes. Each critical bug cost the company 40-80 developer hours in remediation, plus reputational damage.

Solution with ProcessReel: The Senior DevOps Engineer used ProcessReel to capture the exact sequence of actions: updating Jira tickets, merging branches in GitHub, triggering specific Jenkins jobs, verifying logs in AWS CloudWatch, and sending release notifications in Slack. The generated SOP provided an infallible checklist.

Impact:

• Near-Zero Critical Bugs: Post-deployment critical bugs dropped by 90%, virtually eliminating the costly hotfixes and saving thousands of developer hours annually.
• Standardized Deployments: Every deployment now follows the exact same proven procedure, irrespective of the engineer.
• Reduced Deployment Time: Deployments are 20% faster due to clear, unambiguous instructions.
• Faster Onboarding for DevOps: New DevOps engineers can contribute to deployments within their first week, compared to the previous 3-4 weeks of shadowing.

These examples clearly demonstrate that investing in documenting multi-tool processes, especially with the aid of AI-driven tools like ProcessReel, is not merely a "nice-to-have" but a strategic necessity for operational excellence in 2026.

Best Practices for Long-Term Success

Beyond the initial documentation effort, sustained success requires ongoing commitment to these best practices:

1. Centralize Your Documentation: All SOPs, especially those spanning multiple tools, should reside in a single, easily accessible location. Whether it's a dedicated knowledge base, an intranet, or the cloud platform of your documentation tool, ensure everyone knows where to find the latest versions.
2. Assign Ownership: Each critical multi-tool process should have a designated owner (e.g., an Operations Manager, Team Lead, or Subject Matter Expert). This individual is responsible for ensuring the documentation remains accurate and up-to-date.
3. Encourage Feedback: Create a simple mechanism for users to provide feedback on the documentation. A small "Is this helpful?" button or a comment section can yield valuable insights for improvement.
4. Regular Audits and Reviews: Implement a schedule for reviewing and validating SOPs. Quarterly or bi-annual reviews are typically sufficient for most processes, but highly dynamic ones (e.g., software deployment) might need more frequent checks.
5. Link Related Processes: Multi-tool processes often interconnect. Use internal links within your documentation to guide users to related SOPs, creating a comprehensive web of operational knowledge. For instance, a "Client Onboarding" SOP might link to a "Troubleshoot Payment Issues" SOP.
6. Integrate Documentation into Training: Make your SOPs an integral part of your training programs, both for new hires and for continuous learning. Instead of lecturing, guide employees through the documented steps.
7. Embrace Iteration: Accept that documentation is never truly "finished." It's an iterative process of creation, review, refinement, and update. The easier it is to update (which ProcessReel makes significantly simpler), the more likely it is to be maintained.

By adopting these practices, organizations can transform their multi-tool process documentation from a burdensome chore into a powerful asset that drives efficiency, reduces risk, and fosters a culture of operational excellence.

Frequently Asked Questions (FAQ)

Q1: What's the biggest challenge when documenting processes that involve multiple software tools?

The biggest challenge is ensuring consistency and accuracy across the different interfaces and data hand-off points. Each tool has its own nuances, and a slight change in one application's user interface or workflow can invalidate several steps in a multi-tool process. Traditional documentation methods struggle to keep pace with these frequent changes, leading to outdated or inaccurate guides. Furthermore, context switching between tools can be difficult to describe clearly with text alone, making visual documentation critical.

Q2: How much time can AI-powered tools like ProcessReel realistically save in documenting multi-tool processes?

AI-powered tools like ProcessReel can drastically reduce the time spent on documentation. While traditional manual methods (taking screenshots, writing descriptions, formatting) can take hours, or even days, for a complex multi-tool process, ProcessReel can generate a detailed, publish-ready SOP in minutes from a single screen recording. This typically represents a time saving of 80-90% for initial creation and an even greater percentage for updates, as you only need to re-record the changed segments rather than overhaul an entire document. For an Operations Manager, this translates to dozens of hours saved each month across multiple processes.

Q3: Can ProcessReel handle very specific, niche software or custom internal applications?

Yes, ProcessReel is designed to capture actions across virtually any software running on your screen, including niche industry-specific tools and custom-built internal applications. As long as you can perform the process on your computer, ProcessReel can record your interactions (clicks, text input, navigation) and your narration across all these applications. This makes it an incredibly versatile solution for even the most unique multi-tool workflows, transforming previously undocumented or poorly documented proprietary processes into clear, actionable SOPs.

Q4: How often should multi-tool process documentation be reviewed and updated?

The frequency of review and updates depends on the stability and criticality of the process, as well as the underlying tools. For processes involving frequently updated cloud software (e.g., Salesforce, HubSpot), a quarterly review might be appropriate. For more stable, less frequently changed processes (e.g., year-end financial closing), a semi-annual or annual review might suffice. However, any time there's a significant change to one of the involved applications (e.g., a major UI overhaul, a workflow change, or a new feature implementation), the relevant SOPs should be reviewed and updated immediately. Tools like ProcessReel make these ad-hoc updates much more manageable.

Q5: What's the difference between documenting a multi-tool process and a single-tool process?

While both aim for clarity, documenting a multi-tool process adds layers of complexity. A single-tool process focuses solely on interactions within one application, maintaining a consistent interface and terminology. A multi-tool process, however, requires explicit documentation of "hand-offs" between different systems. This includes detailing when to switch tools, what data to transfer (and how), how to reconcile potential discrepancies, and understanding different user interfaces and security protocols. Effective multi-tool documentation must guide the user seamlessly through these context shifts, making strong visual aids and clear explanations of inter-tool actions far more critical than for single-tool processes.

The complexity of modern business operations, driven by a multitude of specialized software tools, presents both challenges and opportunities. Organizations that master the art of documenting multi-step processes across these diverse applications stand to gain a significant competitive advantage in 2026 and beyond. By reducing errors, accelerating training, boosting efficiency, and ensuring business continuity, well-crafted SOPs are not just administrative overhead; they are foundational pillars of operational excellence.

Embrace the power of modern AI tools to transform your documentation strategy. Stop struggling with outdated methods and start creating dynamic, accurate, and easily maintainable process guides.

Try ProcessReel free — 3 recordings/month, no credit card required.