Make with Notion 2025: Simplicity at Scale: Inside Ramp’s AI Operating System (Ben Levick)
Based on Notion's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Ramp’s productivity model targets speed and decision quality together by using AI deep research to enable better, larger decisions.
Briefing
Ramp’s AI operating system pitch boils down to a single operational bet: teams get dramatically more productive when AI is paired with a disciplined way of “building” work—turning vague requests into precise prompts, grounding answers in single-source knowledge, and then wiring outputs into repeatable workflows. The payoff is speed plus quality at the same time, which matters because Ramp’s business goal is to save customers time and money, and because faster, better decisions let teams move faster without sacrificing accuracy.
Ramp’s context is finance and operations, where wasted effort shows up as slow approvals, messy expense work, and constant back-and-forth over where money should go. Ramp frames its mission as becoming the most productive company in the world, backed by years of interest in AI agents and a belief that agentic behavior can shift humans away from busywork toward higher-stakes judgment calls. The company cites large-scale impact—serving 45,000 customers and saving nearly 30 million hours and $10 billion in wasted time and money—while positioning Notion as a partner in that productivity loop.
The core “how” centers on making each team member faster and better. Automation handles manual tasks and delivers information instantly, but Ramp emphasizes a second lever: AI’s deep research capability can improve decision-making by surfacing what matters from large context. That combination—instant research enabling bigger decisions—creates the conditions for team velocity.
Ramp then argues that most organizations stall because they fall into three passive mindsets: “doomers” waiting for AI to replace jobs, “zoomers” expecting one-click tools to do everything without understanding what must be replaced, and “boomers” delaying adoption until the “right way” emerges. The alternative is a fourth mode: “builders.” Instead of treating AI as a black box, builders practice changing the work itself—learning to define tasks, supply the right context, and embed outputs into the tools where work happens.
To operationalize building, Ramp describes three stages: prompt, knowledge, and workflow. For prompt, Ramp gives broad access to tools—ChatGPT, Notion, Notion AI, and Perplexity—so employees must write real prompts rather than rely on hidden automation. Adoption is reinforced with onboarding boot camps, quarterly problem-solving sessions, and an internal Slack channel where people share what they tried and where they got stuck. A key lesson is that vague prompts produce vague results; Ramp recommends an “AI prompt feedback loop,” where AI asks clarifying questions, the user answers, and the user then has AI rewrite the prompt until the output is precise.
For knowledge, Ramp treats knowledge management as a first-class AI risk and advantage. It targets “A+ AI knowledge” as single-sourced, maniacally accurate, crystal clear, and actively taught—because AI systems can amplify outdated or misaligned information across many tools. Ramp uses Notion’s connectors (including Slack, GitHub, Google Drive, and Linear) and builds knowledge feedback loops: when AI answers fail or policies change, humans and agents log the issue, propose updates, and route final truth back to knowledge owners.
For workflow, Ramp focuses on scaling repeatable actions without requiring engineers for every integration. Using tools like Gum Loop, teams can connect triggers and inputs, run AI with the prompt-and-knowledge stack, and write outputs back into systems. Examples include Slack project updates, sales email drafting from research, and operations flows that branch to experts when answers are uncertain. Ramp closes by urging teams to stop waiting for a perfect moment and start building—because practice compounds, innovation spreads internally, and the work becomes more fulfilling when people automate the parts they dislike and reclaim time for judgment and creativity.
Cornell Notes
Ramp’s productivity thesis is that AI becomes truly useful when teams “build” their work end-to-end: precise prompting, grounded knowledge, and repeatable workflows. Ramp says speed and quality rise together when AI can do deeper research instantly, enabling better decisions that let teams move faster. The company warns against three common traps—waiting for AI (“doomers”), assuming one-click tools will replace understanding (“zoomers”), and delaying adoption until the “right” approach appears (“boomers”). Its alternative is a builder model supported by ubiquitous AI access (ChatGPT, Notion, Notion AI, Perplexity), an AI prompt feedback loop to escape vagueness, and knowledge feedback loops that keep single-source information accurate. Finally, workflow tools like Gum Loop let non-engineers wire AI outputs into places work already lives, scaling changes across teams.
Why does Ramp emphasize “faster and better” rather than just automation?
What are the three limiting beliefs Ramp says slow teams down, and what replaces them?
How does Ramp operationalize “prompt” without turning it into generic prompt engineering?
What does Ramp mean by “A+ AI knowledge,” and why is it central?
How do Ramp’s knowledge feedback loops work in practice?
What role do workflow tools like Gum Loop play in scaling AI usage?
Review Questions
- Which part of Ramp’s framework—prompt, knowledge, or workflow—do you think is most likely to fail first in your organization, and why?
- How would you apply Ramp’s prompt feedback loop to a task you currently do using search or spreadsheets?
- What mechanisms would you put in place to ensure AI answers stay aligned with single-source truth as policies and data change?
Key Points
- 1
Ramp’s productivity model targets speed and decision quality together by using AI deep research to enable better, larger decisions.
- 2
Most adoption stalls due to “doomers,” “zoomers,” and “boomers”; Ramp’s alternative is a “builders” mindset that changes how work is done.
- 3
Ramp’s prompt practice relies on ubiquitous access to ChatGPT, Notion, Notion AI, and Perplexity plus enablement that forces employees to write precise prompts.
- 4
An “AI prompt feedback loop” helps users escape vagueness by having AI ask clarifying questions and rewrite prompts based on user responses.
- 5
Ramp treats knowledge management as a first-class AI requirement, aiming for single-sourced, accurate, clear, and well-taught knowledge.
- 6
Knowledge feedback loops combine human review with AI monitoring and proposed updates so knowledge improves after failures instead of staying stale.
- 7
Workflow tools like Gum Loop let teams scale repeatable AI-driven actions without engineering-heavy integration work for every use case.