Donovan Jones / Monkeypaw
Building the operating system development teams have been forced to build by hand
An ambassador partnership and product vision shaped around real development workflow, real market intelligence, and real operational pain.
The industry changed. The workflow never caught up.
Development teams are being asked to do more with fewer people, tighter timelines, and more fragmented information than ever before.
Submissions still come in through messy inboxes. Market intelligence still lives in notes and memory. Writer and director lists still get rebuilt from scratch. Reporting still gets counted manually. And the people closest to the work are still forced to patch together systems that were never designed for development in the first place.
Fragmented tools
Disjointed systems across the development lifecycle.
Manual intake
Submission records still rely on hand entry.
Shared memory
Research repeats when knowledge is not retained.
Lost to reporting
Quarterly updates still get assembled manually.
The best proof of need is that the workflow already exists
Inside Monkeypaw, Donovan rebuilt major pieces of development infrastructure by hand because the existing tools were not enough.
Submission Management
DEV GRIDRedesigned dev grid to manage submission movement, team assignments, and state changes.
Workflow Logic
APPS SCRIPTCustom scripts to move submissions and files across stages automatically.
Market Context
MARKET INTELLIGENCEA dedicated intelligence grid for buyers, mandates, budgets, talent, and deal context.
Portfolio Strategy
SLATE VIEWA slate strategy view to track timing, overlap, executive coverage, and movement.
Intake Experiments
EMAIL AUTOMATIONEarly work on email parsing and structured intake to eliminate repeated manual entry.
The current system works because of effort, not because the infrastructure is good
The problem is not a lack of process discipline. The problem is a lack of purpose-built software for how development actually runs.
Inconsistent Emails
Submission formats vary constantly, so intake still breaks down into manual work.
Automation Breaks
Rules built for one template or workflow collapse when the next edge case arrives.
Repeated Research
Writer and director research keeps getting rebuilt because the system does not retain context well.
Trapped Intelligence
Mandates, deal context, and buyer notes live in disconnected docs instead of one queryable layer.
Limited Visibility
The slate is hard to read dynamically across timing, staffing, overlap, and priority.
Manual Reporting
Quarterly updates still require counting and summarizing by hand when the system should already know.
One system for the work that currently lives everywhere
Greenlit is designed to unify the operational layer of development so teams can spend less time maintaining infrastructure and more time moving projects forward.
Structured inputs, not manual cleanup
Turn fragmented submissions into structured records, routed tasks, and clean development-ready context.
One slate, multiple operating modes
Development, in-progress, and done states stay visible without rebuilding the same context every time.
Share, package, and present without context loss
The same operating data can surface in presentation-ready ways for producers, buyers, or internal leadership.
The command center stays alive
Activity, movement, and momentum are visible as signals rather than buried in another spreadsheet tab.
Core Platform
Build the core development command center
The first phase should prioritize the workflows that remove the most manual friction the fastest.
Structured submission intake from email and attached materials
Unified project and slate workflow views
Assignment tracking across the team
Reusable writer and director database tied to projects
Reporting foundations for recurring rollups and executive visibility
Add the intelligence layer
Once the operational foundation is in place, Greenlit can deepen its value by connecting projects, creatives, buyers, mandates, and real market context.
Buyer and studio mandate tracking
Searchable market-intelligence records
Relationship mapping across projects
Stronger fit signals for packaging strategy
Connect the broader data layer
As Greenlit matures, external data connectivity can make the platform more dynamic, current, and strategic.
RSS feeds and alert-driven updates
News and trade-source integrations
IMDb or comparable data sources
Escrow accounts and investor fund movement
Digital CAMA and waterfall distributions
Treasury, banking, and production cash visibility
This is a category problem, not a one-company problem
Monkeypaw may become a pilot environment. We would welcome that.
But the larger opportunity is to build around the workflow itself: the one used by development executives, assistants, coordinators, interns, and packaging teams across the industry.
Ambassador, with or without a Monkeypaw client relationship
We believe there is a real opportunity to formalize a Greenlit ambassador relationship with Donovan that is independent from whether Monkeypaw becomes a paying client.
Ongoing product feedback
Workflow validation and feature stress-testing.
Market and category insight
A clearer read on evolving studio and development needs.
Strategic storytelling
Helping shape how Greenlit speaks to development teams.
Relationship support
Selective introductions and market-facing credibility where appropriate.
Why this should be an ambassador partnership
Real development workflow knowledge
Context that cannot be simulated from the outside.
Systems thinking under pressure
Proof that the need is real because the workflow had to be built manually.
Lived pain points
Category conviction grounded in the actual work, not a theoretical wishlist.
Market language
Strong articulation of what development teams actually need.
Credibility with the right audience
A trusted voice for the people Greenlit is ultimately serving.
Proposed next steps
Align on ambassador relationship principles.
Confirm the highest-priority Phase 1 workflow needs.
Review a revised prototype shaped around Donovan’s workflow.
Determine whether a Monkeypaw pilot, future-company path, or both make sense.
Formalize ambassador terms in a lightweight agreement.
Make it useful everywhere development actually happens.