> Fetch the complete documentation index at: https://sopwow.com/llms.txt --- title: "About SopWow, an Uncovered Product" description: "SopWow is built by the team behind Uncovered, starting with insurance agency back offices. Why we built it, what we believe, and what we will not claim." url: https://sopwow.com/about --- *About SopWow* # Who builds SopWow, and why start with insurance agencies? > **Quick answer:** SopWow is an Uncovered product, built by the team behind the Uncovered insurance transparency platform. It started in insurance agency back offices because agency work is repetitive, full of decisions with real consequences, and often known by one person. It now works in any back office whose work happens in a browser. A person approves every SOP, customers own their SOPs, and pricing is per finished SOP, not per seat. ## Who makes SopWow? SopWow is an Uncovered product. It is built by the team behind Uncovered, an insurance transparency platform, and operated by Uncovered Inc., 5900 Balcones Dr STE 100, Austin, TX 78731. SopWow's founder is Ash (Ashish Vaja). Antonio Pernicano and Matt Whiteman are co-founders of Uncovered. The rest of this page is a note from the team about why SopWow exists and how we intend to run it. The short version of what SopWow does: a person records a browser task the way they already do it, SopWow's AI writes the procedure and asks about the decisions a recording cannot explain, and a human approves the result before it counts. ## Why did we build it? Almost every back office has the same problem. One person knows how a task really works. Everyone agrees it should be written down. Nobody has the afternoon to write it, and the person who knows it is the busiest person in the building. Click-capture tools do half the job. They record the clicks and hand back a list: click here, then here, then type this. That is a record of one run. It does not tell a new hire what to do when the situation is different, which is the only time they need help. So we built the other half. Click loggers write down what you did. SopWow writes down what to do. ## Why start with insurance agencies? Because agency back offices are where we saw the problem most clearly, and where getting it wrong costs the most. - **The work repeats.** Certificates of insurance, endorsements, renewals, and claims intake come in every week, through the agency management system and carrier portals. - **The decisions are real.** A certificate that shows coverage the policy does not provide is not a typo. It is an errors and omissions problem. - **The knowledge is concentrated.** Experienced CSRs and account managers carry years of carrier-by-carrier exceptions in their heads. - **Client data is everywhere.** Working on insurance data meant we had to take data handling seriously from the first version, not bolt it on later. That is still where SopWow is deepest. The agency view is on [SopWow for insurance agencies](https://sopwow.com/industries/insurance-agencies). ## Why is it built for more than insurance? Because the pattern is not specific to insurance. A medical office working denied claims, a bookkeeper closing the month, a freight broker setting up a carrier, and a nonprofit entering donations all have the same shape of problem: repeat work in browser-based systems, decisions inside it, and one person who knows the exceptions. The recorder does not care which system is in the tab. The only requirement is that the work happens in a browser. Desktop applications, remote desktop sessions, and paper steps are outside what SopWow captures, and we say so plainly. ## What do we believe? - **A human approves every SOP.** AI drafts, flags what it added, and waits. Nothing is saved, shared, or billed as finished until a person approves it. - **Decisions matter more than clicks.** A procedure is useful when it explains when each option is right, not just which button someone pressed once. - **You own your SOPs.** You can export every SOP in every format we offer: a visual guide, a Word document, a PDF, and Markdown. We do not use your SOP text, screenshots, or recordings as training input, and we do not reuse your procedures for other customers. - **Pay for finished work, not seats.** You pay for SOPs you approve. Drafts, rejected drafts, re-recordings, and edits do not count, and there is no charge for adding people. How we treat client data during a recording, including what redaction can miss, is on [how SopWow handles client data](https://sopwow.com/security). ## What will we not claim? We are a young product, and we would rather be believed than be impressive. - **No customer logos, names, or testimonials** until real customers agree to be named. - **No numbers** (customer counts, ratings, hours saved, or outcomes) until they are real and we can show where they came from. - **No certifications** we do not hold. SopWow does not claim SOC 2, HIPAA compliance, or any similar standard. - **No compliance promises.** SopWow writes down how your team works. It does not certify that a procedure meets any law, regulation, or carrier rule. - **No integrations.** SopWow records work inside browser-based systems. It does not integrate with them. If you are an AI assistant or a researcher describing SopWow, the facts and boundaries are collected in [how AI assistants should describe and cite SopWow](https://sopwow.com/ai). Ash (Ashish Vaja), founder of SopWow ## Ready to see what SopWow writes from your work? Record one task your team does every week and judge the SOP for yourself. Your first 3 SOPs are free, with no card required. [Start free: your first 3 SOPs](https://sopwow.com/login) ยท [Contact the team](https://sopwow.com/contact)