cf.doc
![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><g d="M 0 0 L 23 0 L 23 23 L 0 23 Z M 16.5 16.5 L 9.5 16.5 L 9.5 15.5 L 16.5 15.5 Z M 16.5 14.5 L 9.5 14.5 L 9.5 13.5 L 16.5 13.5 Z M 16.5 6.5 L 19.5 6.5 L 19.5 19.5 L 6.5 19.5 L 6.5 16.5 L 3.5 16.5 L 3.5 5.5 L 5.5 3.5 L 16.5 3.5 Z M 7.5 8.914 L 7.5 18.5 L 18.5 18.5 L 18.5 7.5 L 8.914 7.5 Z" fill="transparent" height="23px" id="z3G9kx1V0" transform="translate(0.5 0.5)" width="23px"><path d="M 0 0 L 23 0 L 23 23 L 0 23 Z" fill="transparent" height="23px" id="vOfCJlN56" stroke-dasharray="" stroke-linecap="butt" stroke-linejoin="miter" stroke-miterlimit="10" stroke-width="1" stroke="rgb(255, 61, 0)" width="23px"/><path d="M 7 3 L 0 3 L 0 2 L 7 2 Z M 7 1 L 0 1 L 0 0 L 7 0 Z" fill="rgb(255, 61, 0)" height="3px" id="jOMvHEt6q" transform="translate(9.5 13.5)" width="7px"/><path d="M 13 3 L 16 3 L 16 16 L 3 16 L 3 13 L 0 13 L 0 2 L 2 0 L 13 0 Z M 4 5.414 L 4 15 L 15 15 L 15 4 L 5.414 4 Z" fill="rgb(255, 61, 0)" height="16px" id="QpQR7uybN" transform="translate(3.5 3.5)" width="16px"/></g></svg>)
Product design
Product design
Branding
Branding
Website
Website
Unleash your talents
(2025)
(0)
KPI
90% of interviewed companies want to adopt the tool as soon as possible
10% want to test the product first
(1)
Context
Freeing developers while empowering non-technical teams
Modern product teams rely heavily on a few developers who hold most of the company’s technical knowledge. When they leave, that knowledge often disappears with them.
Modern product teams rely heavily on a few developers who hold most of the company’s technical knowledge. When they leave, that knowledge often disappears with them.
Modern product teams rely heavily on a few developers who hold most of the company’s technical knowledge. When they leave, that knowledge often disappears with them.
Documentation should bridge this gap, yet it rarely does. It’s outdated, too complex, and seldom used. Non-technical teams depend on developers for answers, creating constant interruptions that break focus and slow delivery.
Documentation should bridge this gap, yet it rarely does. It’s outdated, too complex, and seldom used. Non-technical teams depend on developers for answers, creating constant interruptions that break focus and slow delivery.
Documentation should bridge this gap, yet it rarely does. It’s outdated, too complex, and seldom used. Non-technical teams depend on developers for answers, creating constant interruptions that break focus and slow delivery.
cf.doc was designed to reverse that dynamic - giving autonomy to non-technical teams while allowing developers to focus on work that truly matters. The goal was to make documentation living, reliable, and accessible to all, without disrupting existing workflows.
cf.doc was designed to reverse that dynamic - giving autonomy to non-technical teams while allowing developers to focus on work that truly matters. The goal was to make documentation living, reliable, and accessible to all, without disrupting existing workflows.
cf.doc was designed to reverse that dynamic - giving autonomy to non-technical teams while allowing developers to focus on work that truly matters. The goal was to make documentation living, reliable, and accessible to all, without disrupting existing workflows.
(2)
Context
Freeing developers while empowering non-technical teams
cf.doc embeds itself directly into the tools teams already use, such as Notion, Slack and GitHub.
cf.doc embeds itself directly into the tools teams already use, such as Notion, Slack and GitHub.
cf.doc embeds itself directly into the tools teams already use, such as Notion, Slack and GitHub.
A conversational bot integrated within Slack connects to both the company’s documentation and codebase. It understands who’s asking and adapts its response accordingly - offering detailed technical explanations to engineers, and clear, simplified answers to others. Instant access to knowledge, no more constant hand-raising.
A conversational bot integrated within Slack connects to both the company’s documentation and codebase. It understands who’s asking and adapts its response accordingly - offering detailed technical explanations to engineers, and clear, simplified answers to others. Instant access to knowledge, no more constant hand-raising.
A conversational bot integrated within Slack connects to both the company’s documentation and codebase. It understands who’s asking and adapts its response accordingly - offering detailed technical explanations to engineers, and clear, simplified answers to others. Instant access to knowledge, no more constant hand-raising.
Behind Slack, a lightweight web interface allows developers to review and validate automatically generated documentation.
Behind Slack, a lightweight web interface allows developers to review and validate automatically generated documentation.
Behind Slack, a lightweight web interface allows developers to review and validate automatically generated documentation.
Its structure mirrors GitHub’s familiar logic: versions, diffs, validation flows, and roles that ensure quality without slowing teams down. Documentation becomes an evolving layer of the product - always current, always understandable.
Its structure mirrors GitHub’s familiar logic: versions, diffs, validation flows, and roles that ensure quality without slowing teams down. Documentation becomes an evolving layer of the product - always current, always understandable.
Its structure mirrors GitHub’s familiar logic: versions, diffs, validation flows, and roles that ensure quality without slowing teams down. Documentation becomes an evolving layer of the product - always current, always understandable.
(3)
DESIGN & IDENTITY
A sober, intelligent, evolving system
The design direction balances a technical aesthetic with quiet elegance. The interface embraces a dark theme, resonating with developer environments, while gradients animate subtly in the background to embody the system’s character: global, intelligent, adaptable, omniscient.
The design direction balances a technical aesthetic with quiet elegance. The interface embraces a dark theme, resonating with developer environments, while gradients animate subtly in the background to embody the system’s character: global, intelligent, adaptable, omniscient.
The design direction balances a technical aesthetic with quiet elegance. The interface embraces a dark theme, resonating with developer environments, while gradients animate subtly in the background to embody the system’s character: global, intelligent, adaptable, omniscient.
Typography reinforces this precision: TT Hoves for clarity in text, Items for numerical structure and rhythm. The brand avoids excess. Every detail serves clarity, reliability, and focus.
Typography reinforces this precision: TT Hoves for clarity in text, Items for numerical structure and rhythm. The brand avoids excess. Every detail serves clarity, reliability, and focus.
Typography reinforces this precision: TT Hoves for clarity in text, Items for numerical structure and rhythm. The brand avoids excess. Every detail serves clarity, reliability, and focus.
The identity was built to scale. The logo forms the foundation of a flexible system capable of extending into new environments.
The identity was built to scale. The logo forms the foundation of a flexible system capable of extending into new environments.
The identity was built to scale. The logo forms the foundation of a flexible system capable of extending into new environments.
The impact of cf.doc lies in its seamlessness. Teams no longer switch tools to find answers; information flows through the same channel they use to communicate. Developers regain focus. Non-technical teams gain autonomy.
The impact of cf.doc lies in its seamlessness. Teams no longer switch tools to find answers; information flows through the same channel they use to communicate. Developers regain focus. Non-technical teams gain autonomy.
The impact of cf.doc lies in its seamlessness. Teams no longer switch tools to find answers; information flows through the same channel they use to communicate. Developers regain focus. Non-technical teams gain autonomy.
Tests showed a clear reduction in interruptions and a strong sense of fluency in everyday use. Documentation, once ignored, became part of the conversation again: dynamic, shared, and dependable. cf.doc transforms documentation from a static archive into a living system of knowledge ; one that grows, adapts, and keeps teams connected long after individual contributors move on.
Tests showed a clear reduction in interruptions and a strong sense of fluency in everyday use. Documentation, once ignored, became part of the conversation again: dynamic, shared, and dependable. cf.doc transforms documentation from a static archive into a living system of knowledge ; one that grows, adapts, and keeps teams connected long after individual contributors move on.
Tests showed a clear reduction in interruptions and a strong sense of fluency in everyday use. Documentation, once ignored, became part of the conversation again: dynamic, shared, and dependable. cf.doc transforms documentation from a static archive into a living system of knowledge ; one that grows, adapts, and keeps teams connected long after individual contributors move on.
(4)
Credits
Product management
Product management
Product management
Development
Development
Development
![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 160 160" xmlns="http://www.w3.org/2000/svg"><g d="M 0 0 L 160 0 L 160 160 L 0 160 Z M 0 0 L 160 0 L 160 80 L 80 80 L 80 160 L 0 160 Z M 80 160 C 80 115.816 115.816 80 160 80 L 160 160 Z" fill="transparent" height="160px" id="MwgkSCqSr" width="160px"><path d="M 0 0 L 160 0 L 160 160 L 0 160 Z" fill="transparent" height="160px" id="vnRNt0swT" width="160px"/><path d="M 0 0 L 160 0 L 160 80 L 80 80 L 80 160 L 0 160 Z M 80 160 C 80 115.816 115.816 80 160 80 L 160 160 Z" fill="rgb(255, 61, 0)" height="160px" id="M_2ENFmFm" width="160px"/></g></svg>)