Back to Blog Home

Overcoming Blank Canvas Syndrome: Bootstrapping Your Company Brain

Team working at desks in a busy startup office

Do not summarize your chat history. Start from the questions your team keeps answering by hand: choose the ten to twenty that come up most, have an AI draft one page per question from the threads where it was answered, and publish a page only after the person who gave the answer confirms it. A gap sends a new hire to a colleague. A wrong page that the assistant quotes with confidence sends them off to do the wrong thing, so an unconfirmed draft is worse than no page.

Start from questions that were asked twice

The answers already exist, in the threads where your experts replied instead of writing a guide, so you are not starting from a blank page. The hard part is choosing which threads to use. A month of channel history is mostly one-off talk, and your reviewer pays for every line of it. A question asked twice shows real demand, and gives you two answers to compare. Search the channels where people ask for help, such as #engineering-help and #customer-support, for the phrases hires use ("how do I", "where is", "who owns"), count the repeats, and take the top ten to twenty. Then ask the two or three people who answer most often which questions they are tired of answering.

Unfinished Google Docs and Notion pages are the second source, because they hold fragments that never reached chat. Client emails come third, with one caution: a rule agreed with a single client is that client's deal, so leave it out unless the page says whose it is. Scanned forms and PDFs are where a document service such as Google Cloud Document AI, which extracts data from documents like invoices and forms, can help. Chat and email are already text and do not need one.

Export public channels and leave the private ones

For a first batch you can skip the Slack API. On Free and Pro, workspace owners and admins can export messages from public channels as JSON. Private channels and direct messages are not available on those plans; Business+ and Enterprise owners can apply for them, and Slack offers that export for legal and regulatory compliance. We recommend public channels only, even when you could get more: people say things in private that they never meant to publish, and a draft built from them can carry those details into a page everyone can search. Apply the same rule to Microsoft Teams and email by taking shared channels and shared mailboxes, not personal chats or inboxes. Before you send any thread to a model, read your AI provider's data terms for your plan, because whether inputs are retained or used for training differs by product and plan.

On a Free workspace, export first. Slack shows only the most recent 90 days and deletes data older than a year, so the oldest answers are the ones you lose.

Draft one page per question and keep the disagreements

Give the model one thread, or the few threads that answer one question, per call. A month of messages in one prompt invites it to merge unrelated threads and present an old answer as current policy. The prompt below forbids filling gaps, lists what the thread leaves unclear, and skips threads that applied to one case only.

from openai import OpenAI

client = OpenAI()  # reads OPENAI_API_KEY from the environment
MODEL = "..."  # the model your provider currently recommends

PROMPT = """Write one help page from the Slack thread below.
Use only what the thread says. Do not fill gaps.
Title: the question a new hire would ask.
Body: numbered steps.
Source: who answered, and the thread link.
Needs confirmation: every step the thread leaves unclear, and every point a later message disputes.
If the thread applied to one customer or one case only, reply SKIP."""

def draft_page(thread_text):
    response = client.responses.create(
        model=MODEL, instructions=PROMPT, input=thread_text
    )
    return response.output_text

The call follows the interface of the OpenAI Python library. Older tutorials use openai.ChatCompletion.create, which version 1.0 removed (see the migration guide).

When two threads answer the same question differently, do not let the model choose. Keep both answers in the draft and mark the page undecided. We recommend treating these conflicts as findings and not as noise: each one is a question the company never settled, and a new hire gets a different answer depending on who happens to reply. Take them to the owner first. The owner decides, and the page records the decision.

Publish only what the answerer confirmed

Send each draft and its source thread to the person who gave the answer, and ask for one of three replies: right, wrong or out of date. It takes them a few minutes, and they are the one person who can tell, where a general editor can only check that the page reads well. Ask them to strike anything personal or customer-specific while they are there. If the answerer has left, the owner is whoever handles that question now. If nobody does, leave the gap.

Keep unconfirmed drafts where the assistant cannot read them. The assistant looks up your published pages and answers from them, so whatever is in the index becomes the company's answer, and a draft that is probably right is still a guess. Put the confirmer's name and the date they confirmed at the top of each published page, so the next reader knows whom to ask when it goes stale.

Test it with the list you started from

Ask the assistant each question on your list the way a new hire would, in Slack, and sort the results: answered correctly with a source, answered wrongly, or no answer. A wrong answer points to a page to fix. No answer is the honest result for a gap, and the gaps become the next batch. A founder building a guidebook tool for vacation-rental hosts describes the same loop in a comment on an Ask HN thread: the AI organizes the existing information a host pastes in, creates placeholders for what is missing, and logs every question the guidebook failed to answer so the host can fix it. That is one builder's account, not a benchmark.

What to skip for now

Twenty pages do not need fine-tuning, a knowledge graph or a taxonomy project. Retrieval lets a model use an organization's internal knowledge base without retraining it, so a corrected page changes the answers as soon as the index picks it up. Add folders and tags when people start asking where a page is and not what it says.

This week, list the questions you answered by hand, ask the two or three people who answer most for their top five, pick ten, draft those pages from the threads, and send each one to the person who answered it.

Topics

Related posts

Your team’s knowledge, answered in Slack

Add the Kipwise Agent. It answers from your pages with the source, and asks before it changes anything. 7-day trial, no card needed.