PlaybookFounder4 weeks · 7 stepsUpdated 1 November 2026
Start with one team, the sources it already works in and one owner who reads every piece of intelligence. Delegate to people in week two and to an agent in week three. In week four, count what closed on proof, and widen to the next team only when the first one trusts what it gets.
Who it is for, and how long it takes
Who it is for
How long
What you need
What you end with
Founders and executives setting GeniOS up, and the one person who will own the first month.
Four weeks. About an hour on day one, then a short read each morning for the owner.
Read-only access to the first team's email, calendar, chat and the business tools it already uses, plus the sheets and docs where its work is tracked.
One team that trusts its intelligence, a clear view of how much work closed without a person stepping in, and a named next team.
Key takeaways
Start narrow: one team, one owner, the sources that team lives in.
Delegate to people before you delegate to agents, so you learn what a good handover looks like first.
Judge the month by what closed on proof, then choose the next team from where people still had to step in.
Most new tools stall in the first month because they reach everyone at once, and nobody can tell what is working. A narrow start gives you a clean before and after. The same shape works for any new operating routine, with or without software: one team, one owner, a daily habit and a review at the end.
Worked example. The examples use Vaultex, a safety-footwear manufacturer in Greater Noida and GeniOS's first design partner. The buyers, orders and dates are for illustration only.
PrepBefore you start
Settle these seven things before day one.
One team chosen, with a reason you can say in a sentence, such as "sales, because quotes slip".
One owner with 15 minutes every morning and the authority to hand work to others.
The team's main sources listed: email, calendar, chat and its business tools.
A note of what the team is working toward this quarter, to check the goals GeniOS forms.
A rough count of open work today, as your before picture.
A 30-minute review booked at the end of each week.
Agreement that nothing goes out until a person approves it. Setting approval rules puts it on one page.
StepsThe steps
4 weeks · 7 steps
Day 1: pick one team and one owner
Choose the team where work slips most often. For most companies that is sales or the founder's office. Name one person who will read and answer every piece of intelligence for the month. At Vaultex that is sales, and Harsh is the owner.
Days 1 to 3: connect sources, read-only
Connect the email, calendar and chat that team lives in, plus the business tools and sheets where orders and plans sit. Access is read-only to start, so nothing in those tools changes. If you are unsure where to begin, run Which source to connect first before this step.
Week 1: check the goals GeniOS formed
GeniOS forms the company's goals from its own emails, decks and meetings. Read them with the owner and flag anything wrong or out of date. At Vaultex, one goal might be winning the Bata order for 12,000 pairs before Friday's vendor review. A wrong goal usually means the current plan lives somewhere nobody has connected yet.
Week 1: read every morning and answer every item
Read the intelligence each morning and use all four answers: Delegate, Done, Later and Not relevant. Not relevant is as useful as Done, because GeniOS learns from both. An item left unanswered teaches nothing.
Week 2: delegate to people
Use Delegate to hand each situation to the person who owns it, with a date. Mayank gets Bata's request for 60-day payment terms. Anushka gets the clash on Line 2 between the Reebok samples due 15 November and the Bata order.
Week 3: delegate one kind of work to an agent
Hand one repeatable job to an agent, such as a Reply Drafter for the note to the steel toe-cap supplier about its 8% price rise. The agent drafts, and nothing is sent until a person approves. After a week, look at what stayed open, because missing context shows up there.
Week 4: review what closed and pick the next team
Count what closed on proof, what an agent carried with only an approval, and where a person had to step in. The place where people stepped in most points to your next source or team. At Vaultex that might be production and quality, ahead of next month's Adidas vendor audit.
TemplateCopy this week four review agenda
Paste this into the invite for the 45-minute review.
Month one review: [team], [date], 45 minutes
1. What closed (10 min). Items that closed on proof, and anything called done without proof.
2. What an agent carried (10 min). Work that went through an agent with only an approval, and where the approver edited.
3. Where people stepped in (10 min). The three biggest chases or rewrites, and the context missing each time.
4. Goals check (5 min). Are the goals still right? Correct anything in a doc GeniOS reads.
5. Next team (10 min). The next team, its owner, its first source and a start date.
ExampleWorked example: the sales month at Vaultex
How the month might run at Vaultex, with Harsh in sales as the owner.
Week one. Harsh connects his email, calendar and the sales chat groups, read-only. One goal GeniOS forms is winning the Bata order for 12,000 pairs of S3 steel-toe shoes, about $144,000 at $12 a pair, before Friday's 11:00 vendor review. On Wednesday the intelligence shows he promised Bata a quote in a chat message and no email has gone out. He sends it that afternoon.
Week two. Harsh delegates Bata's request for 60-day payment terms to Mayank with a Thursday date, and the Line 2 clash to Anushka. Line 2 is booked for the Reebok samples due 15 November.
Week three. Following Choosing your first agent, Harsh hands supplier follow-ups to a Reply Drafter, starting with the steel toe-cap supplier's 8% price rise. He edits the first two drafts, then approves the rest with small changes.
Week four. Most stepping in happened around the IS 15298 test reports the Adidas vendor audit will ask for next month. Production and quality become the next team, with Anushka as owner.
MistakesCommon mistakes
Most first months go wrong in one of these five ways.
Starting with every team at once. Nobody can tell what worked. Hold the other teams for a month.
An owner with no time. If the owner reads twice a week, items go stale. Pick someone who reads daily.
Leaving items unanswered. An unanswered item teaches nothing. Use Not relevant often, because it is as useful as Done.
Handing work to an agent in week one. Delegating to people first shows you what a good handover looks like. Wait until week three.
Skipping the goals check. Wrong goals skew every later item. Fix them in week one.
What good looks like after
The owner reads the intelligence first thing and answers every item, instead of hunting through threads.
Each open item has one owner and a date, and the team meeting runs from that list.
Promises made in chat, like Harsh's promise of the Bata quote, turn up before the deadline.
At least one kind of reply or meeting goes through an agent and a single approval.
Items close on proof, and anything called done without proof gets a quick question.
You can say how much work agents closed and how often a person stepped in, and you have named the next team.
If the owner still checks every thread by hand at the end of the month, find the missing source or context, add it, and run week three again.
How to know it worked
Compare day 30 with the before picture from day one, using plain counts. Once the month is done, a no-dashboard Monday keeps the habit going, and What is company intelligence? explains the idea behind it.
What to measure
How to check it
A good sign
Open items with one owner and a date
Count the open list on day one and on day 30
Nearly every item has both by week four
Items closed on proof
Count items marked done where the email, calendar or record confirms it
Most closes carry proof by week four
Work an agent carried with one approval
Count drafts approved with no edits or small ones
Rises from week three to week four
Times a person had to step in
Count the chases and rewrites the owner did by hand
Falls week to week and points to the next team
Questions
Do we need to connect every tool on day one?
No. Start with the tools the first team uses every day. Each source you add later widens the context GeniOS reasons with, so widening is a matter of connecting the next one.
Will GeniOS send anything on our behalf?
Nothing is sent until a person approves. GeniOS thinks and delegates. Agents such as a Reply Drafter or a Scheduler draft, and a person approves before anything goes out.
What if the goals GeniOS forms are wrong?
Raise it in week one, before you lean on the intelligence. Goals come from your own emails, decks and meetings, so a wrong goal often means the current plan lives somewhere GeniOS cannot read yet. Put it in a doc GeniOS reads, and tell us on a call.