AI applied to real work

Less hype. More work that actually moves.

Understand where ChatGPT, Claude, Codex, Lovable, skills, plugins and connectors fit before adding another tool to your company.

THE STACKDOCS TEST
  1. What outcome must change?
  2. Which data and permissions does it need?
  3. Where does a person approve?
  4. How will we know it worked?
Start with a decision

Questions already showing up at work.

Every guide includes a useful case, a bad fit and the primary sources behind the analysis.

01 · Foundations

Skills, plugins, connectors and MCP: what each one actually does

A practical way to decide whether you need to teach AI a method, connect an account or expose a tool.

Read · 16 min
02 · Tool choice

ChatGPT, Claude, Codex or Lovable: where each tool fits at work

Stop asking which AI is best. Identify the work, environment and degree of control you need.

Read · 15 min
03 · Processes

Organize the process before asking AI to automate it

A lean method for turning a messy routine into a workflow that can be delegated, measured and improved.

Read · 14 min
04 · Meta

Instagram, Facebook and Threads in a business workflow

What Meta platforms can contribute to an operation, and why automatic posting is only a small part of the job.

Read · 15 min
05 · Operational security

How to connect Drive, Slack, CRM and email to AI without granting too much access

A practical method for choosing permissions, starting with read access and keeping sensitive actions under review.

Read · 16 min
06 · Processes

From meeting to follow-up: an AI workflow that improves delivery without adding another system

Turn meeting decisions into owners, deadlines and next steps without maintaining a parallel operation.

Read · 15 min
07 · Skills

Seven company routines that can become reusable AI skills

Concrete recurring work that can be packaged as instructions, decision rules and consistent outputs for AI.

Read · 17 min
08 · Product

Lovable and Codex in the same project: where prototyping ends and development begins

Use visual speed and repository-oriented work together without losing decisions, tests or technical ownership.

Read · 16 min
Our editorial filter

A product feature is not a business outcome.

01

Process first

We begin with the work, owner and expected output before choosing a product.

02

Primary sources

Capabilities and limits are checked against official product documentation.

03

Useful limits

We state when an approach creates more cost, risk or maintenance than value.

04

Human review

Public claims, sensitive decisions and irreversible actions keep a responsible owner.

Early access

Help shape the StackDocs workflow library.

Tell us which recurring process is wasting time inside your company.

Share a workflow →