AI by Design · A Kitala Program
Before we build your plan
A plan only fits if it is built around what is actually there. Your business, your team, and the way the work already runs. This document is how we learn all three before we spend time together.
Answer what you know. Skip what does not apply. We are after an accurate picture, not a polished one.
- What you get back. A short written read on what we see in your answers and where we would start. High level, and yours to keep either way.
- How long this takes. About 30 minutes. Not every question needs a deep answer.
- Your answers stay on your computer while you type. Nothing is sent until you press Send.
- You can stop and come back. This page remembers where you left off in your browser. Files are the one exception, so attach those in the session you send from.
- The ones marked Must are the ones we cannot give you anything useful without. Everything else sharpens it.
01
You and the company
Who we are talking to and what the business actually does.
Company and where to send the readMust
Two or three sentences in your own words. What work comes in, what goes out, who pays for it.
Roughly how many people
Round numbers are fine. If the second one is the whole company, say so.
Time lost, errors caught late, work redone, things that fall through the cracks. Not the hardest problem. The one that keeps costing you.
02
What you want out of this
Your side of it. What you are after, and what you want us to be careful about.
Be specific. “The team uses AI” is not specific. “Our estimators spend six hours a week less on first drafts” is.
Cost, the effect on your people, security, quality of the work, whether it sticks after we leave. Name the real one. A plan that does not account for it is not worth building.
03
Where AI sits today
What is already in place. Whatever the answer is, including nothing at all, it changes what we would recommend.
04
What has been tried
The honest version of this is worth more than the tidy version. Nothing here counts against you.
“We bought licenses and people stopped using it after week three” is a useful answer.
Best guess is fine. Excitement, quiet worry about their jobs, eye rolling, confusion.
05
The work you want off your plate
The most useful section in this document. Three tasks described properly beat thirty listed in shorthand.
Five is plenty. Include the ones where you only need to glance and approve, not just the ones you would hand off completely.
One per line. Put a name or a role against each one if you can.
06
What we have to design around
Constraints are not obstacles here. They decide which version of this is even worth proposing.
HIPAA, SOC 2, customer contracts that rule out certain tools, regulated industry requirements, anything your insurer cares about.
07
Anything you want us to read
Optional, and it changes the quality of what we send back. If you have it already, send it. Do not build anything for this.
One limit worth knowing. Everything you attach here has to add up to under 8 MB, and it is one file per box. Slide decks run large. If something will not fit, send it to hello@kitala.io and we will match it up. The counter at the bottom of this section tracks your total.
No files attached yet.
08
The call
Last section.
What happens next
We read what you send, spend some time on your company, and come back with a short written read. What we see, what we would start with, and what we would leave alone for now. That usually lands within a few business days.
Then we talk. If the read is useful and you want to go further, we will tell you what that looks like. If it is not the right time, you keep the read and we leave it there.
Questions before you send this: hello@kitala.io
AI by design means designing it with your team. Not for them.
