Why I am building Nexpanion in public

Where I am starting

I am not a professional software developer. I started by using AI in work I already had: building websites, preparing content, scheduling posts, and reducing repetitive steps.

The more I experimented, the more I saw that the hardest part was not finding a tool. It was choosing a useful problem, describing the requirements clearly, and checking whether the result actually helped.

This website is the first project

I used Nexpanion as the first practical test. Starting with a sitemap and a demo, I rebuilt the site with a separate URL for every article, Vietnamese and English content, member accounts, and four resources that require sign-in to download.

The less visible work took most of the time: configuring email and Google authentication, restricting file access, connecting the subscription form, adding analytics consent, testing mobile layouts, and preparing a rollback path. That work gives me firsthand material to document instead of a summary of someone else’s tutorial.

What Nexpanion will document

I will publish tutorials, experiment logs, tool comparisons, and downloadable resources. Each post will try to state the test conditions, time, cost, failures, and the parts that still require human review.

The site will be organized around jobs rather than tool names: building websites, automating operations, selling across channels, creating visuals, and supporting customers.

Why I am writing in public

Public writing forces me to explain my work in plain language. It also creates a more honest record of ability: results, decisions, failed attempts, and corrections.

You do not need a technical background to read Nexpanion. You need a piece of work you want to improve and a willingness to start with a small version.

My working principles

• Start with the problem, not the tool.
• Build a small version before a large system.
• Clearly label plans, tests, and verified results.
• Include failures, costs, and manual steps.
• Return to primary sources for external claims.

How you can take part

Subscribe for one practical experiment each week, create a free account to download checklists, or send me a task you would like to automate. Real questions will help Nexpanion decide what to build next.