Create Your AI Stack

An AI stack is the collection of tools you use to get work done. It might be three apps you already know, connected by a simple routine. You do not need a subscription to everything with an AI button.

Use the builder above to make your choices visible. Drag a tool into the area where it will help, or choose an area and use its add button. You can move a tool later, remove it, and share the stack with someone else.

Start with the work, then choose the tools

“I need an AI stack” is a broad ambition. “I want to turn customer conversations into a clear product brief every Friday” gives you something to build around.

Write down the result you want, who will use it, and what currently slows you down. Add that goal to your stack so you can judge every tool against the same purpose.

Give each tool a job

The canvas has five areas to help you think through a workflow. These are suggested roles, not fixed product categories. Put a tool where it makes sense for your work.

• Think & research: explore questions, compare ideas, and work through source material.
• Build & ship: create a website, write code, store application data, and publish the result.
• Create & communicate: turn ideas into writing, audio, video, or other outputs people can use.
• Capture & organize: keep the notes, knowledge, and project context your work depends on.
• Connect & automate: move information between tools and handle repeatable steps.

You can use the same product for different kinds of work. The builder keeps one copy of each tool so you can choose its main role in this stack. You do not need to fill every area.

Try a small stack before building a large one

Here are three starting points to explore. They are examples you can adapt, not a list of tools everyone needs.

Everyday thinking and writing

Try ChatGPT for working through a brief, Notion for organizing decisions, and Wispr Flow for capturing a rough draft by voice. The handoff is simple: capture the idea, develop it, then keep the version you intend to use.

Build a website

The setup behind this website uses Codex, GitHub, and Cloudflare. Codex helps make changes, GitHub keeps the project history, and Cloudflare publishes the site. Follow the website-building guide to explore that workflow.

Turn a conversation into useful content

Try Granola to capture meeting context, Claude to shape a draft, and HeyGen to explore a short video explanation. If a repeatable handoff emerges, investigate whether Make can connect the relevant steps. Check each output against the source conversation before publishing.

Check the handoffs

A collection of good tools can still produce a messy workflow. Walk through what happens when information leaves one tool and enters the next.

1. Input: what does the next step need—a transcript, a file, a structured record, or a clear brief?
2. Transfer: will you copy and paste, export a file, use an integration, or build an automation?
3. Review: who checks the result before it becomes a decision, a client message, or published content?

Manual handoffs are often enough while you are learning what works. Automate a step once you can describe it clearly and recognize when it has failed.

Choose a model as well as an app

An application and its underlying AI model are different choices. An app might offer several models, while a coding environment adds access to files and development tools around the model.

Use the model-selection guide and interactive benchmark graph to shortlist candidates. Then compare them on your own task. A model score alone does not tell you whether the whole setup will work well for your team.

Run one real task through your stack

Choose something small enough to finish. Keep a record of the time spent, the corrections required, and any handoff that felt awkward.

• Did the final result meet the brief?
• Could you explain how it was produced?
• Did you spend less time doing the work, or just move the effort into checking it?
• Are two tools doing the same job without a clear benefit?
• Can a colleague repeat the workflow?

Keep the tools that earn their place. Remove or replace the rest. A small stack you understand is easier to improve than a large one you rarely use.

Save your stack and make the next step concrete

The builder saves your draft in this browser when browser storage is available. Use Download stack for a Markdown copy you can keep, or Copy stack link to share the selected tools, their areas, the stack name, and its goal. Anyone with that link can open the shared configuration.

Each tool card links to its tool guide, with features and video tutorials. If you want to turn the stack into a working team habit, plan a workshop around the tools and tasks you have chosen.