Confidential · May 2026
× DayDream
A phased proposal for the complete DayDream operating system, with CRM / black book and intake as the first build and a roadmap that expands into the rest of the company workflow.
Commercial production OS
Design Partner Proposal · May 2026
Why this matters now
DayDream is not a giant machine. It is a small, high-output shop carrying commercial work, experiential work, live broadcast, and post/VFX pressure at the same time. That means the system has to be light, current, hard to break, and able to grow into a complete operating system for the company.
People are moving quickly
The same project can be in motion, in discussion, and half-formed at the same time.
Context is scattered
Slack, Gmail, memory, and sheets all hold pieces of the answer, but none of them are the answer.
Less fragility
Greenlit becomes the operating layer that keeps the team from rebuilding the same context every week.
The current workflow runs on effort,
not on a system built for the work
Bids, directors, and status scattered across Slack, Gmail, sheets, and memory.
| Date | Client / Agency | Project | Format | Status |
|---|---|---|---|---|
| Jan 6 | Nike x Wieden+K | Runner Series | TVC :60 | In Pre-Pro |
| Jan 14 | Budweiser / DDB | Game Day Spot | TVC :30 | Bid Pending |
| Jan 22 | Liberty Mutual | Agent Redirect | TVC :15/:30 | Passed |
| Feb 3 | Gatorade / TBWA | Athlete Stories | Doc Short | Bidding |
| Feb 9 | Verizon / Grey | Spring Brand Film | TVC :15/:30 | New Bid |
Briefs arrive in different shapes
Every new bid comes in a little differently, so intake still needs a person to sort it out.
Rules break on the next edge case
What works for one format falls apart when the next agency or producer sends it a different way.
The same context gets rebuilt again
Director notes, talent context, and client history keep getting rewritten because they are not linked.
Reporting is still manual
When the system should already know the status, somebody still has to pull it together by hand.
The work is carrying the system
The operation moves because the team keeps the context in their heads and in their inboxes.
Visibility drops when things get busy
Once bids stack up, it gets harder to see what is live, what is dead, and what needs a decision.
Why scattered tools create gaps
Slack and Gmail are good channels. They are not the system. DayDream needs the job jacket, the black book, and the intake record to stay tied together so the team can keep moving when the work comes in hot.
Slack is fast, not durable
It keeps the conversation moving, but it does not hold the record the team needs later.
Gmail is complete, not structured
Everything is there, but it still has to be interpreted and moved into the right place.
Sheets are editable, not reliable
They work until the team needs ownership, linked records, and version control.
Memory is useful, but it is not searchable
The best context often lives in one person's head. That does not scale across the shop.
What Greenlit changes
Greenlit becomes the record the team trusts, so the channels stay flexible without turning the workflow fragile.
The intelligence layer sits on top
Phase two uses the job jacket and black book history to recommend the right people, the right reels, and the right angle for the bid.
The full operating system
Phase one starts with the black book and intake layer because that is the part the team can use right away. The rest of the roadmap builds on the same workflow, each phase adding more of the operating system until the full picture is in place.
CRM / black book
This is not a passive address book. It is the place where DayDream can see who knows whom, who is attached to what, what is active, what is dead, and which reel set belongs on which bid.
Relationship context
The same person can mean different things in different bids. The black book needs to hold that nuance without forcing duplicate records.
Reel curation
One director may need a different reel set depending on whether the ask is documentary, comedy, tabletop, or something more versatile.
Recommendation layer
The system should be able to suggest the right angle for the bid based on the brief, the look, and the feel.
Intake
Turn incoming briefs and opportunities into structured records instead of scattered messages. Keep the process customizable so it reflects DayDream's commercial workflow rather than forcing a generic template.
Pull from Gmail / Slack
Normalize the message into one record instead of leaving it across multiple threads.
Human review
Nothing critical gets finalized without a person approving the record.
Feed the pipeline
The intake record becomes the source of truth for the CRM and bid status.
What intake solves
The team stops treating every new opportunity like a fresh manual data-entry exercise.
Where it starts
Gmail and Slack are the inputs. The structured record is the output. The human stays in control.
How it works
A brief lands, gets normalized into intake, and updates the black book automatically — one loop that keeps the whole team current without extra admin.
To: DayDream / Development
Date: May 1, 2026 · 11:58 AM
Please see the attached brief for a fast-turn commercial bid. We need director options, reel recommendations, timing, budget signal, and an internal read as soon as possible.
Happy to set up a call if helpful.
— Marcus
Brand: DayDream client
Owner: Anthon
Different by bid context
Outcome still open
What is active vs dead
Rollout plan
Phase one ships in four to six weeks — narrow enough to move fast, clear enough to hand off internally on day one.
Investment
A fully custom operating system built for DayDream — not configured, not approximated. Nothing off the shelf does 90% of the job. This does. Priced as a complete bespoke build with white-glove delivery across three phases.
$990 / month · $99 per seat · 10 seats
If each seat recovers 3 hrs/week, the system pays for itself in week one.
| Phase | % | Amount |
|---|---|---|
| Phase 1 kickoff | 50% | $5,940 |
| Phase 2 delivery | 25% | $2,970 |
| Phase 3 completion | 25% | $2,970 |
| Total | 100% | $11,880 |
Future phases
The roadmap gets bigger after phase one, but the shape stays the same: keep the job jacket current, surface the right context, and make the next decision easier than the last one.
Relationship intelligence
Use the history in the system to show who knows whom, which relationships are warm, and where the right context sits on a bid. This is the layer that starts recommending the right people and the right angle.
Job jacket
Pull the working jacket into the system: crew lists, schedules, call sheets, run of show, and the rest of the handoff material that DayDream keeps moving by hand today.
Reporting and automation
Connect more feeds, reporting, approvals, and downstream workflow once the core system is trusted and in use. That is where the fuller operating layer starts paying off.
Why Greenlit
DayDream gets one system that keeps the work moving, keeps the job jacket current, and leaves the team with fewer things to chase by hand.