"Document later" is how teams say "document never" - Incentius Blog Home - Incentius - Enable Digital Transformation [![Logo](/img_astro/incentius-logo.svg)](/) Solutions About [Case Studies](/portfolio/) [Blogs](/blog-posts/) [Career](http://aurochs.freshteam.com/jobs) Open main menu ![Menu icon](/img_astro/menu1.png) [Get In Touch](/contact/) Solutions [![](/img_astro/generative-black.svg) ![](/img_astro/brain-green.svg) Voice AI](/voice-ai/) [![](/img_astro/product-development-black.svg) ![](/img_astro/product-development.svg) Product Development](/product-engineering/) [![](/img_astro/generative-black.svg) ![](/img_astro/brain-green.svg) Generative AI](/generative-ai/) [![](/img_astro/data-black.svg) ![](/img_astro/database-green.svg) Data Engineering](/data-engineering/) [![](/img_astro/mvp-black.svg) ![](/img_astro/rocket-green.svg) Data & Analytics](/data-analytics/) [![](/img_astro/cloud-black.svg) ![](/img_astro/computing-green.svg) DevOps & CloudOps](/devops-and-cloudops/) About Us [![](/img_astro/product-black.svg) ![](/img_astro/product-green.svg) About Us](/about-us/) [![](/img_astro/team_black.svg) ![](/img_astro/team_green.svg) Team](/team/) Solutions ![](/img_astro/dropdown-arr.svg) [ ![](/img_astro/generative-black.svg) Voice AI ](/voice-ai/)[ ![](/img_astro/product-development-black.svg) Product Development ](/product-engineering/)[ ![](/img_astro/generative-black.svg) Generative AI ](/generative-ai/)[ ![](/img_astro/data-black.svg) Data Engineering ](/data-engineering/)[ ![](/img_astro/mvp-black.svg) Data & Analytics ](/data-analytics/)[ ![](/img_astro/cloud-black.svg) DevOps & CloudOps ](/devops-and-cloudops/) [Blogs](/blog-posts/) About ![](/img_astro/dropdown-arr.svg) [ ![](/img_astro/product-black.svg) About Us ](/about-us/)[ ![](/img_astro/team_black.svg) Team ](/team/) [Case Studies](/portfolio/) [Career](http://aurochs.freshteam.com/jobs) [Get In Touch](/contact/) "Document later" is how teams say "document never" Yash Pukale 1. May 25, 2026 2. 4 min read ![](/_astro/Screenshot_2026-05-25_at_1.52.26PM.width-1000_ZP1i8H.webp) **"Document later" is how teams say "document never"** We learned this the hard way on a recent project. The setup: a multi-tenant system where onboarding each new tenant meant repeating a precise 15-step ritual. A config here. A table there. A reconciliation rule. A UI entry. The first time, our lead engineer just knew. The second time, he half-remembered. The third time, an "obvious" step got skipped, a deploy went sideways, and our team spent two hours retracing what should have been a thirty-minute task. Sound familiar? ## **The cost of "later"** Every team we've worked on pushes documentation to a separate sprint that never quite happens. Tickets get shipped. PRs get merged. Slack threads decay. The system grows in a way that only its three original authors can still navigate. New hires onboard slowly. Clients ask questions that nobody can answer without paging the senior engineer. The codebase quietly becomes a fortress of tribal knowledge. The myth is that documentation is expensive to write. The truth is that retro-documentation - sitting down six months later trying to reconstruct decisions from git history - is what's expensive. ## **What we changed** On this project, we tried something different: documentation lived inside the repo, deployed alongside the application, and got written as part of every feature - not after. We used **VitePress** to render a documentation site directly from the same git repository as the code. Push the code on Monday, push the doc update in the same PR, the site rebuilds, the team sees the change in minutes. No separate Confluence space. No parallel wiki to drift out of sync. The docs aged at exactly the same rate as the code. Three things this unlocked for us: ### **1\. Architecture decisions stopped getting lost.** Every non-obvious decision - why we picked one pattern over another, what alternative we rejected and why - got a short page. Six months later when someone asked "why is it built this way?", the answer was a link, not a meeting. ### **2\. Client expectations became reviewable.** When the client wrote in Slack "make sure new tenants work the same way," we converted that into a written page describing what "the same way" actually meant. The client reviewed it, agreed, and we had a shared definition of done before a single line of code shipped. No more launch-day "wait, I thought it would do X" surprises. ### **3\. Architecture diagrams stopped being throwaway.** Diagrams used to live in Slack screenshots, slide decks, Lucidchart exports - all eventually stale, none authoritative. With everything in one site, the diagram lives next to the prose that explains it, and they age together. If the diagram is wrong, the page is wrong, and someone catches it in code review. ## **Where AI fits in** The argument against documentation has always been time. AI changed the math for us. We now draft documentation pages with an LLM in ten minutes that would have taken us an hour. Architecture writeups, runbooks, onboarding playbooks, even the long tenant-onboarding guide - all started as AI-drafted skeletons that we then edited for accuracy and tone. Here's the part most people miss: **AI is great at drafting, not at deciding.** The human still owns the decisions. AI doesn't know why our team picked one pattern over another - we do. AI doesn't know what our client cares about - we do. AI takes the draft from blank-page-paralysis to 70% done; the team does the last 30%. This shifts everything. Documentation used to be a multi-hour tax. Now it's a fifteen-minute task. At that price point, "document later" stops being defensible. ## **Why this applies to any project** This isn't specific to the domain we were working in, or to the stack we used. It's a pattern: * A docs site (VitePress works well; pick what fits your team) generated from the same repo as the code * Architecture decisions written as you make them, not after * Client expectations captured as written, reviewed artifacts * Diagrams stored next to the prose, not in separate tools * AI as the drafting partner, the team as the editor Whether it's a payments platform, a CRM, an analytics pipeline, or an internal admin tool - the same pattern holds. **The cost of documenting has collapsed. The cost of not documenting has not.** ## **The shift** "Document later" used to be a reasonable trade-off when documentation was expensive. It isn't anymore. Our new rule: **a feature isn't done until the doc page is updated.** If that sounds like overhead, run the experiment for one sprint. You'll get the hours back from the meetings, the Slack threads, and the bug investigations that good documentation quietly prevents. **What's the documentation gap your team is dragging around right now - the one nobody has time to fix?** About Author ![](/_astro/yash.width-300_frHNF.webp) Yash Pukale ![](/img_astro/thumb.png) ### See What Our Clients Say ![](/img_astro/left-chevron_1.svg) ![](/img_astro/left-chevron_2.svg) ![](/img_astro/mind-gap-crop.svg) Mindgap Incentius has been a fantastic partner for us. Their strong expertise in technology helped deliver some complex solutions for our customers within challenging timelines. Specific call out to Sujeet and his team who developed custom sales analytics dashboards in SFDC for a SoCal based healthcare diagnostics client of ours. Their professionalism, expertise, and flexibility to adjust to client needs were greatly appreciated. MindGap is excited to continue to work with Incentius and add value to our customers. Samik Banerjee Founder & CEO ![](/img_astro/trusted-by-businesses/worldatwork_coloured.webp) World at Work Having worked so closely for half a year on our website project, I wanted to thank Incentius for all your fantastic work and efforts that helped us deliver a truly valuable experience to our WorldatWork members. I am in awe of the skills, passion, patience, and above all, the ownership that you brought to this project every day! I do not say this lightly, but we would not have been able to deliver a flawless product, but for you. I am sure you'll help many organizations and projects as your skills and professionalism are truly amazing. Shantanu Bayaskar Senior Project Manager ![](/img_astro/trusted-by-businesses/gogla_coloured.webp) Gogla It was a pleasure working with Incentius to build a data collection platform for the off-grid solar sector in India. It is rare to find a team with a combination of good understanding of business as well as great technological know-how. Incentius team has this perfect combination, especially their technical expertise is much appreciated. We had a fantastic time working with their expert team, especially with Amit. Viraj gada Gogla ![](/img_astro/trusted-by-businesses/humblex_coloured.webp) Humblx Choosing Incentius to work with is one of the decisions we are extremely happy with. It's been a pleasure working with their team. They have been tremendously helpful and efficient through the intense development cycle that we went through recently. The team at Incentius is truly agile and open to a discussion in regards to making tweaks and adding features that may add value to the overall solution. We found them willing to go the extra mile for us and it felt like working with someone who rooted for us to win. Samir Dayal Singh CEO Humblx ![](/img_astro/mind-gap-crop.svg) Transportation & Logistics Consulting Organization Incentius is very flexible and accommodating to our specific needs as an organization. In a world where approaches and strategies are constantly changing, it is invaluable to have an outsourcer who is able to adjust quickly to shifts in the business environment. Transportation & Logistics Consulting Organization Consultant ![]() Mudraksh & McShaw Incentius was instrumental in bringing the visualization aspect into our investment and trading business. They helped us organize our trading algorithms processing framework, review our backtests and analyze results in an efficient, visual manner. Priyank Dutt Dwivedi Mudraksh & McShaw Advisory ![](/img_astro/mind-gap-crop.svg) Leading Healthcare Consulting Organization The Incentius resource was highly motivated and developed a complex forecasting model with minimal supervision. He was thorough with quality checks and kept on top of multiple changes. Leading Healthcare Consulting Organization Sr. Principal ![](/img_astro/mind-gap-crop.svg) US Fortune 100 Telecommunications Company The Incentius resource was highly motivated and developed a complex forecasting model with minimal supervision. He was thorough with quality checks and kept on top of multiple changes. Incentive Compensation Sr. Director Most Read [ ![](/_astro/ChatGPT_Image_Apr_2_2025_12_06_35_PM.width-1000_ZUChn3.webp) Optimizing Large-Scale Data Exports: FastAPI, GraphQL, and AWS S3 Struggling with slow, inefficient file downloads in your application? Generating and handling large file downloads can be a nightmare—UI freezing, server overload, and endless waiting. ![](/_astro/Vinay_Chaudhari.width-300_1QPJnB.webp) Vinay Chaudhari 1. Apr 08, 2025 2. 4 min read ](/blog-posts/optimizing-large-scale-data-exports-fastapi-graphql-and-aws-s3/)[ ![](/_astro/Screenshot_2025-04-02_at_12.09.33_PM.width-1000_ZyU6y1.webp) How to Build a Web Search Agent with Phidata: A Step-by-Step Guide Phidata is an **open-source framework** for building AI agents with capabilities like memory, tool use, and reasoning​ It’s model-agnostic and supports various large language models (LLMs), allowing developers to turn any LLM (like OpenAI GPT or local models) into a functional **search agent**. ![](/_astro/Kartik_Puri.width-300_1YNCyp.webp) Kartik Puri 1. Apr 02, 2025 2. 4 min read ](/blog-posts/how-to-build-a-web-search-agent-with-phidata-a-step-by-step-guide/)[ ![](/_astro/e20f5335-cbf6-414c-a096-7d2849109cff.width-1000_15DfBS.webp) Migrating to Soketi: Improving Our Real- Time Communication Architecture Our journey with real-time data communication has evolved significantly. Initially using Flask-SocketIO with Vue, we faced several challenges that led us to seek a more robust solution. ![](/_astro/pratik.width-300_Z2vB9eu.webp) Pratik Patel 1. Mar 17, 2025 2. 4 min read ](/blog-posts/migrating-to-soketi-improving-our-real-time-communication-architecture/)[ ![](/_astro/startup-employee-looking-business-charts-usin.width-1000_2knrAp.webp) Understanding AI Agents: A Comprehensive Guide to AI Agentic Workflows In the rapidly evolving landscape of artificial intelligence, AI Agents have emerged as a transformative technology that represents far more than just industry jargon. ![](/_astro/chetan_piucv.width-300_ZK3Vor.webp) Chetan Patel 1. Feb 28, 2025 2. 4 min read ](/blog-posts/understanding-ai-agents-a-comprehensive-guide-to-ai-agentic-workflows/) ## We use cookies We use cookies to improve site. Some cookies are necessary for our website and services to function properly. Other cookies are optional and help personalize your experience, including advertising and analytics.You can consent to all cookies or decline all optional cookies. Without a selection, our default cookie settings will apply. I agree I decline [![logo](/img_astro/logo.svg)](/) Incentius is a technology and professional services company providing analytics, operations and product engineering services. [![facebook](/img_astro/facebook.svg)](https://www.facebook.com/Incentius/)[![twitter](/img_astro/twitter.svg) ](https://x.com/incentius/)[![linkedin](/img_astro/linkedin.svg)](https://www.linkedin.com/company/incentius/posts/?feedView=all) ![location](/img_astro/pin.svg) Office No.201B, 2nd Floor, Beta-1, Giga Space IT Park, Viman Nagar, Pune - 411014, Maharashtra, India ![email](/img_astro/message-icon.svg) info@incentius.com ![phone](/img_astro/telephone.svg) +1 (302) 415 3208 ![](/img_astro/secure-footer.svg) ![](/img_astro/secure-footer-mobile.svg) * Solutions * [Voice AI](/voice-ai/) * [Generative AI](/generative-ai/) * [Data Engineering](/data-engineering/) * [Product Development](/product-engineering/) * [Data & Analytics](/data-analytics/) * [DevOps & CloudOps](/devops-and-cloudops/) * [UI/UX Design](/ui-ux-design/) * Recent Blog * [Medallion Architecture in Practice: Six Layers, One Source of Truth](/blog-posts/medallion-architecture-in-practice-six-layers-one-source-of-truth/) * ["Document later" is how teams say "document never"](/blog-posts/document-later-is-how-teams-say-document-never/) * [Your Business & AI - What It Actually Means for You](/blog-posts/your-business-ai-what-it-actually-means-for-you/) * [How Internal Agent-Built Software Reduced Our SaaS Dependency](/blog-posts/how-internal-agent-built-software-reduced-our-saas-dependency/) * [MarkItDown: A Powerful Utility for File Conversion to Markdown](/blog-posts/markitdown-a-powerful-utility-for-file-conversion-to-markdown/) * [Python 3.14: A Game-Changing Release for Modern Development](/blog-posts/python-314-a-game-changing-release-for-modern-development/) * [Building a RESTful Blog API with Flask and Swagger: A Complete Guide to Streamlined API Development](/blog-posts/building-a-restful-blog-api-with-flask-and-swagger-a-complete-guide-to-streamlined-api-development/) * [Tailwind CSS 4.0 vs 3.x: What Changed and How We Implemented It](/blog-posts/tailwind-css-40-vs-3x-what-changed-and-how-we-implemented-it/) * [The Future of AI: What to Expect in the Next 5 Years](/blog-posts/the-future-of-ai-what-to-expect-in-the-next-5-years/) * Menu * [About](/about-us/) * [Blog](/blog-posts/) * [Career](http://aurochs.freshteam.com/jobs) * [Case Studies](/portfolio/) * [For Startups](/startups/) * [Let's Talk](/contact/) © Copyright 2025 Incentius [Request Site](/) [Terms and Conditions](/) [Privacy Policy](/privacy-policy/)