Cassiano F.

Most SaaS and API companies don't have a writing problem, they have an ownership problem. AI generates drafts, engineers push updates, someone creates a docs drafts, and suddenly your technical documentation is outdated, your support team is still fielding the same questions, and nobody's accountable. I fix that. Whether you need a one-time project done right or a technical writer to own your documentation long-term, I treat every engagement like a product, not a task. I'm an Expert-Vetted technical writer with 7+ years of experience and a background in software engineering. I've helped 100+ SaaS and API-first companies cut support tickets by 50% and increase product adoption by 80% by building documentation that stays accurate, useful, and scales with the product. What I can take off your plate: ✅ API Documentation: REST, OpenAPI, Webhooks, Auth, SDKs ✅ SaaS Documentation & Product Guides ✅ Help Center & Knowledge Base Architecture ✅ Developer Portals & Developer Documentation ✅ AI Product Documentation & Integration Guides ✅ User Manuals, Tutorials & Onboarding Documentation ✅ Documentation Audits, Revamps & Content Gap Analysis ✅ Technical Blogs, Whitepapers & Explainers Why not just use AI? You can, and you probably have. The problem isn't generating content. It's that AI writes but doesn't own. It doesn't know when something breaks, when a new feature changes a workflow, or when a user manual is quietly misleading your customers. I use AI where it adds speed, like drafts, code samples, and consistency checks. I apply my own judgment where it matters, bringing my expertise to strategy, structure, technical accuracy, and accountability. You get documentation that moves faster than hiring an agency and is more reliable than running on AI alone. How I work: 1️⃣ Audit your existing technical documentation and surface gaps costing you users 2️⃣ Define a content architecture and documentation strategy before writing a word 3️⃣ Write precise, workflow-driven content, no filler, no feature dumps 4️⃣ Deliver on time, with clear communication throughout 5️⃣ For clients who want ongoing coverage, I scale the engagement, keeping documentation current as the product evolves I work directly with engineering, product, DevRel, and founders. I'm proficient with Readme, Docusaurus, Mintlify, Fumadocs, Stoplight, GitBook, Swagger, and Postman, and I integrate into your team via Slack or Microsoft Teams from day one. If you want a technical writer who takes genuine ownership of your documentation and stays accountable for the results, let's talk.