Repurposing Dev Tools for Business Intelligence

I recently started using a tool called Antigravity. It’s built by Google DeepMind. It is designed for “coding.” It lives in my terminal. It reads my file system. It helps me write software.

But I realized something 48 hours in: I wasn’t using it for code.

I was using it to architect businesses.

The “Context Aware” EA

Most AI tools (ChatGPT, Claude web) are “amnesiac.” You have to paste in your context every time. Coding agents, however, are designed to “read the repository.” They understand the entire file structure of a project.

So, I created a “repository” that had zero code. Instead of src/components, I had src/strategy. Instead of index.js, I had manifesto.md.

Documentation implies Code

When you treat your business documentation like a codebase, magic happens.

• Version Control: You can see how your strategy has evolved.
• Modularity: You break big ideas into small, reusable “components.”
• Linting: You can have the AI “debug” your business logic.

I asked Antigravity to “scan my client-onboarding.md and tell me where the friction points are, based on the churn-logs.md file.” It didn’t need a prompt engineer. It just read the files and gave me the answer.

The Future of Ops

We are moving toward a world where “Business Operations” and “Software Engineering” use the same toolchain. IDE-driven-strategy. Markdown-based-management. Terminal-based-thinking.

The tools are ready. We just have to use them “wrong” to get it right.