Brief your employee like a real hire
An employee that knows your business well enough to stop asking — and to push back.
The steps
- Write the one-page company brief — Every strong output traces back to context. Give it once, properly:
> Here's the brief. We sell {what} to {who}. Our customers choose us because {why}. We never {taboo — discounting, jargon, competitor X's tone}. Our goal this quarter is {goal}. Keep this in mind for everything you do.
That message is worth more than fifty small prompts — it's the difference between an assistant and an employee.
- Put the reference documents in Files — Anything you'd hand a new hire on day one belongs in the employee's **Files** tab: price list, tone examples, the deck, last quarter's numbers. Files persist across every conversation — chat context doesn't have to.
- Correct in the moment, not in bulk — Feedback lands best right after the output it corrects. "Too formal — rewrite it the way I'd say it to a friend" teaches more than a style guide. Corrections go to memory; you should notice fewer repeats within a week.
- Ask for pushback explicitly — By default an employee optimizes for doing what you asked. Upgrade it:
> When my request is a bad idea, say so before doing it, and propose the better version.
The first time it stops you from sending a mediocre campaign, this line will have paid for the whole setup.
You should see
New conversations start from knowledge instead of zero — and the outputs sound like your company.
The OpenLabor Academy