How to Make a Company AI-Native (without building anything)

Ramp published a post about Glass, the internal AI productivity suite they built for every employee. It's impressive work: auto-configured integrations, reusable skills, persistent memory, scheduled automations, Slack-native assistants, and 350+ skills reaching 99% adoption. Their post is worth reading in full. Many teams are already using Devin this way, including our own at @cognition. It's all built in so you don't have to build any of it yourself. Here's how to set it up. What Devin is Devin is an AI software engineer and teammate that can write code and analyze data. Each session runs in its own cloud VM with a code editor, browser, terminal, and shell. Your repos are cloned, dependencies installed, and tools connected before Devin starts working. For data and analytics, Devin includes a specialized Data Analyst Agent (DANA) that queries your databases, builds visualizations, and answers business questions. On top of this, Devin has a platform layer: integrations, reusable skills, persistent knowledge, org-wide playbooks, and scheduled automations. You configure these once and they apply across your entire team. Glass built these capabilities as custom internal software. Devin ships them as configuration. Integrations AI is useful when it can reach your tools. An engineer asks Devin to trace a Sentry error, check the recent PRs that touched the affected code in GitHub, and open a fix, all in one session. A sales lead asks Devin to pull a prospect's activity from HubSpot, cross-reference it with usage data in the database, and draft a personalized follow-up. Both work because everything is already connected. Devin does this out of the box. Your org admin connects tools once, and every person on the team gets access to all of them in every session. Devin has native integrations for GitHub, GitLab, Bitbucket, Azure DevOps, Slack, Microsoft Teams, Jira, and Linear. On top of that, the MCP Marketplace has 100+ additional integrations like Notion, Sentry, Datadog, Figma, PostgreSQL, Salesforce, Stripe, HubSpot, and BigQuery. Most are one-click OAuth. For internal tools, you point Devin at your own API endpoint. Once connected, Devin creates PRs, responds to issues, posts updates in Slack threads, queries your databases, and pulls context from any connected tool, all without per-session setup. To set it up: Go to Settings > Integrations for native tools, or the MCP Marketplace for everything else. Skills and Playbooks When someone figures out the best way to test a frontend change, investigate a production error, or deploy to staging, that workflow should be available to everyone else on the team immediately. Devin has two mechanisms for this: Skills and Playbooks. Skills Skills are `SKILL.md` files committed to your repos. They define reusable procedures like testing before a PR, deploying to staging, investigating a codebase, and scaffolding a service. They follow the open Agent Skills standard, so the same files work across multiple AI tools. Place them at `.agents/skills/<skill-name>/SKILL.md`. Devin's backend indexes skill files across all connected repositories, so your team has a shared catalog of procedures. Devin matches skills to the task at hand, so repo-specific skills only activate when working in that repo. When someone asks Devin to fix a bug in that frontend repo, it activates `test-before-pr` before opening the PR. It won't fire when working on a different repo. Skills support `$ARGUMENTS` for parameters, `` !`git branch --show-current` `` for live context injection, and `allowed-tools` to restrict Devin to read-only operations for investigation tasks. Devin itself also suggests creating skills. After it learns something about your setup during a session, it proposes a `SKILL.md` and gives you a Create PR button. Every skill committed is immediately available to everyone on the team. Playbooks Playbooks are org-wide reusable prompt templates. They live in the Devin web app, are shared across your organization, and can be attached to any session. Playbooks have macros, short identifiers like `!investigate`, so anyone can attach one by typing the macro name when starting a session. Enterprise customers can push playbooks across all organizations. To set it up: Go to Settings > Playbooks. For skills, commit `SKILL.md` files to your repos. Knowledge Your team has conventions and context that determine whether AI output is generic or useful. "MRR is stored in cents, not dollars." "Never deploy on Fridays after 3pm." "Active user means at least one event in the past 30 days." When the AI knows these things, every task gets better output. Devin's Knowledge system stores this persistently. Tips, instructions, and context persist across all sessions, and Devin recalls relevant knowledge based on what it's working on. You create knowledge in Settings > Knowledge with a trigger and content: Trigger: "deploying to production" Content: "Always run the full E2E suite against staging before deploy