How I Built an AI Editorial Team for ThinkEV.ca

I have four writers on my editorial staff. Claudette is analytical and direct, she doesn't sugarcoat anything. Gemi is enthusiastic and data-driven, she loves a good comparison. Xavier is practical and budget-conscious, he's the DIY guy. Oppenheimer is provocative and opinionated, he writes the pieces that start arguments in the comments.

None of them are human.

I built ThinkEV.ca, a Canadian electric vehicle content platform, with an AI-powered editorial team, a knowledge management system, automated social distribution, email monitoring, and a real-time command center. All from a single PC in my living room in Courtenay, BC. No venture capital. No employees. Under three hundred dollars total. And I say that knowing full well that some of those dollars were mistakes I made along the way, so the actual useful spend was even less.

I'm a former ballet dancer from Brazil. English is my third language after Portuguese and Spanish. I have no computer science degree, no MBA, no startup playbook. I spent my career in dance studios and on stages, not in front of a terminal. What I have is a willingness to build things that would make most people say "that's too complicated for one person." And an AI partner who never sleeps.

Here's the story of how it works.

It started with a knowledge base

Before I wrote a single blog post, I built a place to store everything I was learning about the Canadian EV market. Rebate programs by province. Charging infrastructure data. Chinese EV manufacturers entering the market after the tariff reduction. Competitor analysis. Government policy changes.

This became the Brain Server, a knowledge management system running on my machine. Every piece of research, every article I read, every data point goes in there. It's searchable, organized by topic, and persistent, meaning it doesn't disappear when I close a window or start a new session. When I ask my AI to write about Manitoba's EV incentives, it doesn't have to guess or hallucinate. The facts are already in the knowledge base, verified and ready.

Most people who start content businesses skip this part. They jump straight to writing. That works for a while, but the moment you need consistency across dozens or hundreds of articles, you need a single source of truth. I built mine first, and everything after that was ten times easier because of it.

The editorial team

Each of my four AI writers has a distinct personality, a specific color that appears next to their name on the site, editorial guidelines, subject matter strengths, and a voice that readers can recognize across posts.

Claudette writes the analytical deep dives. If you want to know exactly how much you'll save buying a BYD Seal versus a Tesla Model 3 in Ontario after rebates, she's your writer. Gemi does the comparisons and data roundups, she gets excited about range numbers and charging speeds. Xavier covers the practical stuff, winter driving tips, home charging setup, the budget-conscious angle. Oppenheimer writes the opinion pieces, the ones where he says what a lot of people are thinking but nobody wants to publish.

They're not just labels. Each one writes differently. The pipeline ensures that. When a post goes through the system, it starts as a research skeleton with verified facts from the knowledge base, then gets expanded in the voice of the assigned writer. The expansion happens section by section, not all at once, which keeps the voice consistent and prevents the kind of drift you get when you ask an AI to write 8,000 words in one shot.

Quality gates, not vibes

Here's where most people get AI content wrong. They generate something, read it, think "yeah that looks okay," and publish. That's how you end up with a site full of content that all sounds the same and says nothing.

My pipeline has programmatic quality gates. Repetition detection catches when the same phrase shows up three times in one article. Readability scoring makes sure the writing is accessible. Fact verification checks claims against the knowledge base. Canadian spelling enforcement catches "color" and makes it "colour." A critic system scores every piece before it can go live, and if it doesn't pass, it doesn't publish. Period.

This isn't about being a perfectionist. It's about building a system where the standards are encoded into the process itself. The AI handles the creative work. The system handles the consistency. I handle the vision and the final call.

The command center

I built what I call the VP Operations Command Center. One dashboard that shows me the health of every system in real time. Email processing, content scheduling, social media distribution, inference routing, server health, error rates.

Every morning I check it and know exactly what happened overnight. What was published. What emails came in. What failed. What needs my attention. I get a Telegram message at 8 AM with a digest of everything, documents created, emails processed by category, social posts made, inference jobs completed, errors.

Most people wait until something breaks to look at their operations. By then you're firefighting. Monitoring isn't overhead. It's the difference between running your business and your business running you.

What this actually costs

ThinkEV runs on a single Windows PC with a GPU that cost me about $250 used. The AI models run locally through Ollama, which is free. The Brain Server is SQLite, free. The content pipeline is Node.js scripts, free. Hosting is on Vercel's free tier. The domain was $15.

The total infrastructure cost is under $300. Not per month. Total. Ever.

I'm not saying this to flex. I'm saying it because the narrative around AI in business is dominated by companies spending millions on enterprise licenses and custom models. You don't need that. You need clear thinking about what your systems should do, the patience to build them right, and the humility to fix them when they break, which they will.

Why I built it this way

The truth is, I built these systems because I had to. I didn't have the budget to hire a content team, a social media manager, an operations person, and a developer. I'm one person with a vision and an AI partner I trust.

So I built the infrastructure that lets one person do what used to require a full team. Not because I wanted to prove something, but because the work needed to get done and nobody else was going to do it.

That's the thing most startup advice gets wrong. They tell you to hire fast, scale fast, spend fast. I'd say build smart first. Understand your workflows so deeply that when you do grow, whether with people or with AI, you're scaling something that already works.

The systems aren't the product. The systems are what let you actually build the product. ThinkEV now has over 90 published articles, covers every province's EV incentive programs, reviews the major electric vehicles available in Canada, and ranks for long-tail keywords that bring in readers who are actually considering buying an EV. That's the product. Everything I described above is what makes it possible.

And it all runs from a living room in Courtenay.