My AI workday: from a rough brief to a published article

The building-in-public article on this site began with a simple request: add a post about what building in public is like for Ashley. That short brief became an article, a homepage feature, and a page readers could visit.

The useful part of that example is the sequence of decisions between the request and the finished page. AI helped with writing and implementation. The site’s actual structure, established background, and limits on what was known shaped the result.

1. Give the work a purpose

The job was to introduce the experience behind The Wealth Experiment in a first-person voice. The page needed to feel connected to the site and give readers a practical next step.

A useful brief also establishes boundaries. In this case, the article could discuss the work and the approach. It could not make up sales, testimonials, reader reactions, or a dramatic personal story to make the writing more persuasive.

2. Use what already exists

The existing blog, homepage, venture directory, and publishing structure provided context. That mattered because a new article had to fit the design, link to real resources, and appear in the places readers and search engines could find it.

For your own work, gather the approved background, audience, examples, tone, and destination before asking for a draft. When a detail is unknown, mark it as unknown rather than asking the tool to fill the gap.

3. Inspect the draft for substance

Ask whether the article makes a useful point, whether a reader can act on it, and whether the first-person statements are things the author can stand behind. Fluent writing needs the same factual and editorial attention as any other draft.

Here, the finished article discusses experience, unfinished work, AI, attention across ventures, and a weekly update structure. The reader can use that structure without buying anything or supplying an email address.

4. Publish the whole reading experience

The implementation included the article page, a homepage card, a blog listing, the author and publication date, and discovery through the sitemap and RSS feed. The page also connects to the Lab, workflow maps, and workshop.

Those details are part of finishing the job. A document that looks complete in a chat still needs a home, working links, and a way for the intended reader to reach it.

5. Verify what you can actually verify

For that release, the content build and syntax checks passed. The existing marketing and tool checks passed, including internal links and article discovery. After deployment, the article, homepage, and blog responded successfully and contained the new story.

That establishes publication and the checks performed. It does not tell us whether readers found the article valuable or changed their behavior. Those are questions for feedback and usage evidence.

Borrow the workflow

1. State the audience, purpose, deliverable, and boundaries.
2. Provide approved source material and identify missing facts.
3. Ask for a draft with specific examples and useful next steps.
4. Review claims, voice, links, and completeness.
5. Publish it where people can find and use it.
6. Check the live result, then decide what feedback to collect.

This example is not a timed productivity benchmark. Its value is a process you can inspect and adapt. Start with the AI workflow maps if you want help choosing one part of your work to practice.

Follow Ashley’s founder journal · Try the build-along challenge · Get email notes