The origin of Document360 involves whistles. In December 2017, more than 40 people at Kovai.co split into 15 teams inside the company’s Coimbatore office. They held daily stand-ups and a larger “scrum of scrums” to catch dependencies. Each person received a whistle to blow when help was needed, or when something small had gone right. The assignment was to make a working version of a new documentation product in 14 working days.
The resulting prototype was rough. Much of its code would soon be thrown away. Yet the sprint answered the question that mattered: could a company then known for specialist Microsoft integration software build a useful knowledge-base platform of its own? The team believed it could. Eight years later, Kovai.co said Document360 had crossed $10 million in annual recurring revenue, without outside funding.
That tidy result can make the beginning sound like a stunt. It was not. Founder and CEO Saravana Kumar had spent months studying documentation tools, prices and gaps, while interviewing his own documentation team. Kovai.co had struggled to maintain help content for BizTalk360. The software existed, but the explanation of the software kept becoming a product problem too.
The product hiding inside the support queue
Nearly every growing software company accumulates an accidental second product: the body of instructions required to use the first. It lives in help articles, API references, release notes, onboarding checklists, standard operating procedures and the experienced support rep’s memory. When those pieces drift apart, customers submit tickets and colleagues repeat answers. The cost arrives as thousands of small interruptions.
Document360 gives that material a governed home. Teams can publish a public help center, keep internal knowledge private, manage workspaces and languages, control roles, review versions and watch analytics for failed searches or weak articles. The platform also handles user manuals and API documentation. Its current pitch is broader than page publishing: one source from which websites, widgets, chatbots and AI assistants can retrieve answers.
The practical appeal is less glamorous than AI, and more durable. A writer can set a workflow before a page is published. A product manager can see what readers search for but fail to find. A support team can embed relevant answers where questions appear. Developers can import an OpenAPI specification instead of hand-formatting every endpoint. Global teams can maintain localized versions without treating each language as an unrelated site.
This is where specialist tools make their case against a shared folder or a broad workspace. Notion is supple and familiar. ReadMe concentrates on the developer experience. ClickHelp brings the traditions of technical authoring. Zoho and eGain connect knowledge to larger suites. Document360’s chosen territory is the operational middle: enough structure for enterprise governance, without asking every contributor to become a documentation engineer.
“Document360 came out of our own pain points as we struggled to build a good documentation or knowledge base for our product BizTalk360.”Saravana Kumar, founder and CEO
A launch is a decision, not a finish line
After the hackathon, Kumar returned to London and reshuffled the company’s priorities. Around eight engineers stayed with the new product. They cleaned up the experiment, discarded prototype code that would not survive production and rebuilt with a longer horizon. That sequence matters. The two-week sprint created proof and momentum; it did not suspend the ordinary physics of software.
The company’s account of its first 100 customers contains another telling detail. Kumar initially bought document360.io because the dot-com address carried a premium and the project’s viability was uncertain. Later, Kovai.co paid $10,000 for document360.com. A domain purchase is not a business milestone, but this one works as a small marker of conviction arriving after evidence.
Company-wide hackathon creates the MVP.
The product passes 100 paying customers.
Kovai.co reports its 1,000th customer.
Document360 2.0 is introduced.
Kovai.co acquires interactive-demo platform Floik.
Document360 crosses $10 million ARR, according to Kovai.co.
The product passed 100 paying customers in under two years and hit 1,000 in 2022, according to Kovai.co. Document360 2.0 followed in 2023. In 2024, the parent company acquired Floik, a Bengaluru product that turns workflows into interactive demos, step-by-step guides and explainer videos. Six Floik engineers, including founder Vidyasankar Krishnamurthy, joined the effort. The move acknowledged something documentation teams already know: sometimes showing the click path beats describing it.
By late 2025, the company said Document360 had become its second product to reach $10 million ARR. Kovai.co also described the product as a central source of its recent growth. Kumar set a target of $25 million ARR within the next three years. Those numbers come from the company, which is privately held, but their specificity gives the market a useful reference point for a category that rarely attracts consumer-tech attention.
AI raises the cost of a bad source
Document360 now presents AI as a layer across the system. Eddy AI can help draft, rewrite, summarize and translate. It can turn video, audio or transcripts into articles. Conversational search and chatbots answer questions against approved material, while the company says its search responses cite their sources. Its MCP server is designed to let assistants such as ChatGPT, Claude and Copilot connect to a knowledge base.
These additions reflect a shift in who reads documentation. The audience used to be a person scanning a navigation tree. Now it may be a support bot retrieving a passage or an agent attempting an action. Machines are fast literalists. They amplify stale instructions, duplicate policies and ambiguous names. A polished chatbot over a neglected knowledge base merely delivers the wrong answer with less friction.
That tension is healthy for Document360. Generative tools can make writing cheaper, potentially weakening the case for expensive authoring software. At the same time, they increase the need for permissions, review, provenance and a reliable source of truth. The company’s durable value will depend less on how many AI buttons fit in an editor and more on whether teams can trust what comes out.
AI can shorten the distance to an answer. It cannot decide which answer deserves authority.
What teams can steal from the story
The founder lesson is tempting to reduce to “build your own painkiller.” The sharper version is to examine recurring operational pain with enough patience to separate a market from a personal annoyance. Kumar catalogued competitors, prices and missing features before calling the hackathon. He also had an existing company, engineers who understood enterprise software and customers who demonstrated the cost of poor documentation.
The product lesson is to design a loop, not a library. Knowledge is captured, reviewed, delivered, measured and revised. Analytics matter because publication is not completion. A search with no useful result is product feedback. A support ticket answered for the fifth time is a candidate article. An obsolete page is technical debt wearing prose.
The buyer lesson is to choose around the work. A small team that needs an adaptable internal wiki may be happier in Notion. A developer portal may favor ReadMe. A technical publishing group with complex output formats may look at ClickHelp. Document360 becomes more compelling when several audiences, approval steps, languages and delivery surfaces must share one governed source. Migration effort, total cost, editor preferences and integration fit still deserve a trial with real content.
A revealing trial is not a pristine five-page demo. Import a neglected manual with duplicate titles, broken links and three people claiming approval rights. Ask one new employee and one impatient customer to find the same policy. Then change that policy and trace every place it appears. A platform earns its keep when the update is visible, reviewable and hard to miss. Buyers should test exports and permissions too. Knowledge can outlive a vendor relationship, and a useful system should make both access and departure legible.
And the AI lesson is almost old-fashioned: clean the cupboard before inviting a faster cook. Assign owners. Archive contradictions. Measure failed searches. Decide which content may be public, private or available to an agent. The retrieval layer cannot rescue a company that declines to maintain what it knows.
There is also a people question hiding inside the software choice. Someone must own the taxonomy, settle competing definitions and retire pages that no longer describe reality. Document360 can expose the gap and route an article through review. It cannot manufacture accountability. A sound implementation pairs tooling with a simple social contract: named owners, visible review dates and permission to delete. Otherwise the knowledge base becomes a more searchable attic.
The quiet infrastructure of understanding
At the $10 million celebration, Kovai.co employees dressed in black and blue and gathered outdoors to form a human “10M” for a drone. The formation took several attempts. People shifted, checked the view from above and shifted again. It is a neat image for documentation work: local positions only make sense when someone can see the whole system.
Document360 still has to prove that its widening platform remains coherent as AI chatbots, interactive demos, API references and traditional help centers converge. It also faces capable rivals with different strengths and much larger ecosystems. But its central observation has aged well. Software does not end when the feature ships. Somebody must explain what happens next.
The 14-day prototype made that explanation into a product. The years after made it into a business. In an era filled with machines that promise instant answers, Document360 is selling the less instant work beneath them: structure, ownership and the discipline to keep the source true.
Five useful questions
What is Document360?
It is a cloud platform for creating, governing and publishing public or private knowledge bases, product documentation, SOPs, user manuals and API references.
Who owns Document360?
Document360 is a product of Kovai.co, the bootstrapped enterprise software company founded and led by Saravana Kumar.
When was it founded?
The product was conceived and prototyped in December 2017, then launched commercially in 2018.
What does Eddy AI do?
Its features support conversational search, drafting, rewriting, summarization, translation and content generation from media. Teams should still review generated material for accuracy.
How does it differ from Notion or ReadMe?
Notion is a broad collaborative workspace, while ReadMe focuses on developer and API experiences. Document360 positions itself across customer support, internal knowledge, SOPs, manuals and API documentation with governance controls.