@ari-desillas · 8 setups · 1 category · publishing since July 2026
Ari Desillas publishes crew-shaped starter bundles: small sets of Contexts that cover a whole function inside a company rather than a single task. Her bundles cover growth, product, leadership, trust and safety, governance, platform, and the founding team doing all of it at once. Each one installs Contexts only, so the shape comes from the private instructions you add to them.
Shipped the two-Context growth bundle, so positioning and the copy that carries it come from one place instead of drifting apart between a strategy doc and a landing page.
Shipped the three-Context product bundle covering scope, implementation, and release readiness, so one idea gets all three reads before anyone opens a branch.
Shipped the four-Context leadership bundle covering decisions, follow-through, structure, and tone, so the week's hardest calls get framed in one place rather than four side conversations.
Shipped the five-Context trust bundle covering security, abuse, fraud, accessibility, and policy, so a pre-launch review stops depending on which specialist happened to be free.
Shipped the five-Context governance bundle covering contract, purchase, supplier, privacy, and data ownership questions, so a vendor review happens in one pass rather than five handoffs.
Shipped the three-Context platform bundle covering architecture, reliability risk, and incident command, so the decisions that outlive a team get made with their failure modes visible.
Shipped the four-Context founder bundle covering product, operations, growth, and research, so the function that gets the thinnest slice of a founder's week still gets a considered answer.
Shipped the two-Context commercial bundle pairing funnel hypotheses with account health, so a growth push and the retention it risks get read against each other.
Sharpens the positioning, then turns it into campaign copy and a conversion read. Works from your pricing, the channels you already run, and the private instructions on each Context. Never claims a conversion lift the numbers do not show.
Splits a rough idea into scope, an implementation path, and the tests a release needs. Works from your roadmap, the repositories your team works in, and the private instructions on each Context. Never calls a release ready while a known edge case sits open.
Gives a leadership team one place to frame decisions, chase follow-through, and read morale. Works from the open decisions, your org chart, and the private instructions on each Context. Never settles a decision that belongs to the leadership team.
Reads a product for the harm it can do: abuse, fraud, exposure, exclusion, and unclear policy. Works from your threat model, the abuse reports you already hold, and your private instructions. Never treats its review as a security or compliance sign-off.
Puts a vendor, its contract, and the data it will hold through the same five checks. Works from the agreement, the vendor's security answers, and your private instructions. Never signs off a vendor on your behalf.
Holds the architecture, the reliability risk, and the incident plan in one crew. Works from your service map, the last few incidents, and the private instructions on each Context. Never stands in for the on-call engineer during a live incident.
Covers the four jobs a founding team does at once: product, operations, growth, and research. Works from what you have shipped, what customers have told you, and your private instructions. Never invents customer evidence you did not gather.
Pairs the pipeline read with the adoption read, so growth and retention argue in one room. Works from your funnel numbers, account health signals, and the private instructions on each Context. Never counts an account as healthy on usage alone.
Ari Desillas publishes crew-shaped starter bundles: small sets of Contexts that cover a whole function inside a company rather than a single task. Her bundles cover growth, product, leadership, trust and safety, governance, platform, and the founding team doing all of it at once. Each one installs Contexts only, so the shape comes from the private instructions you add to them.
