For any team or business

Practical AI workflows, without the theater.

We publish what we learn about practical AI workflows: the articles and First Look, where you can watch the checks. We will publish the studies we run on our own site.

Studies

What we study on our own site

No study is published yet. The decision-model studies are next, and each one will state the question, the method, the sample, the dates, the findings, and the limits. First Look is the live checks page.

The method

Start with the work, not the model.

Pick the job first: research, analysis, reporting, planning, review. Then decide what context, tools, checks, and output it actually needs. A workflow written this way has the same five parts.

Read the method

Illustration of a practical AI workbench connecting files, data, tools, and review.
  1. Source materialFiles, notes, sites, transcripts, spreadsheets, and records that ground the task.
  2. Tools and agentsSearch, APIs, databases, MCP servers, and browser actions, with clear boundaries.
  3. Reusable instructionsPrompts, skills, templates, and checklists that turn one-off requests into workflows.
  4. Evidence and reviewCitations, checks, limits, and human judgment before anything is trusted or sent.
  5. Useful artifactsReports, briefs, pages, plans, and dashboards people can inspect and reuse.
WebMCP, running here

Try the tools on this site.

Most sites make agents scrape and guess. Here, the forms declare themselves as tools an agent can call, with named inputs, plain descriptions, and a person reviewing anything that gets sent.

11tools a browser agent can call on this site

  • Declared, not scrapedTools are declared in the page markup, so an agent calls the form instead of guessing at the layout.
  • Bounded on purposeEvery tool here is read-only or reviewed intake. Nothing is answered or acted on automatically.
  • Same result for peopleWithout an agent, the same buttons run the same functions. Accessible labels serve both.

Checks the title, meta, H1, declared tools, llms.txt, and robots.txt on one page. Open First Look to watch an agent use it.

index.htmldeclarative WebMCP
<!-- The Ask form below, as an agent sees it -->
<form action="/api/ask" method="post"
  toolname="ask_rafalai"
  tooldescription="Submit a practical AI or
    educational topic question to RafalAI for review.">

  <input name="email" type="email" required
    toolparamdescription="The sender's email
      address for the response.">
  <!-- name, topic, message … -->
</form>

Tools on /first-look

  • Explain this pageexplain_this_page
  • List the public pageslist_public_work
  • List the briefslist_documents
  • Explain the briefexplain_document
  • Show the briefshow_document
  • Set a URLset_their_url
  • Run a first lookrun_first_look
  • Check pasted HTMLscan_html
  • Read the current lookget_first_look
  • List questionslist_questions
About

What we do

RafalAI is a new practice. We write about practical AI workflows and show the checks in First Look. We will publish the studies we run on our own site. We do not have past client work to show yet.

Write to us on the contact page, or follow along on LinkedIn.

Ask a question

Stuck on something? Ask.

Questions about using AI for real work: a workflow that isn't holding up, a prompt, a tool, a source you can't verify, or a claim you want checked.

  • A person reads every question.
  • Your browser agent can fill this form for you. It is the ask_rafalai tool.
  • Want something built instead? Tell us about the work.

A person reviews every question before anything is sent back. If a follow-up is useful, you'll get an email reply. Privacy