u/KangJay_

Self-promo disclosure: this is mine.

Online ESL has a weird math problem sometimes:

50-minute lesson.

45 minutes finding material.

20 minutes adapting it.

Another 10 fixing the answer key.

😐

I built Chalkline to attack that part.

Put in something like:

B1 adults / job interviews / 60 minutes / vocabulary + reading + speaking

and it builds an editable lesson package around those constraints.

Student material, teacher copy, answer key, individual-question editing/regeneration, and then you can reuse the completed material as homework, quizzes, Bingo, etc.

I'm deliberately not trying to make an “AI teacher.” You're still choosing what your students need. This is supposed to remove production work after you've made that decision.

There's a free plan here:

chalkline.flashodds.live

If you already have a lesson coming up, I'd be curious how it handles the exact thing you were going to prepare anyway.

Self-promo disclosure up front: I built this.

One thing I kept noticing with ESL teaching is that knowing what you want to teach isn't necessarily the time-consuming part.

It's everything after that.

Turning “A2 simple past, 50 minutes, some controlled practice and a speaking activity” into an actual worksheet, teacher copy, answer key, homework, etc.

So I built Chalkline.

You give it:

• topic
• CEFR level
• age group
• class length
• the kinds of exercises you want

It builds the lesson structure first and then generates the content inside that structure. The result is editable, printable material with a matching teacher copy and answer key.

You can also regenerate one bad question without blowing up the rest of the lesson, which was something I really wanted to get right.

Finished lessons can also become things like homework, quizzes, Bingo sets, and Taboo decks.

There's a free plan if you want to throw an actual lesson you're teaching at it:

chalkline.flashodds.live

I’d much rather hear “this part would annoy me in a real class” than generic feedback, so feel free to beat the hell out of it.

I have spent the past year building a large collection of software projects, and I recently realized that the projects make more sense as a portfolio than as isolated startups.

The umbrella is Flash AI Solutions, an applied AI product studio.

A few examples:

Rebid Radar: finds public K-12 contract renewal and rebid signals for regional technology providers.

Flash Outreach: a human-approved research and outreach system that keeps evidence, contacts, campaign history, and replies connected.

Flash Props: a sports projection API and MCP interface, initially focused on competitive Call of Duty and other esports.

Chalkline: generates printable and interactive lesson activities from a teacher’s topic and difficulty requirements.

The shared engine is collecting difficult information, organizing it, and turning it into something operational.

My current challenge is not finding more products to build. That machine is working almost too well. The challenge is deciding which product has the clearest buyer and shortest route to a paying customer.

From the four examples above, which one can you understand fastest without additional explanation?

I am especially interested in whether the “applied AI product studio” positioning makes the portfolio feel coherent or whether it still sounds too broad.

A subscription customer churned recently, which pushed me back into first-dollar mode.

The uncomfortable part is that I do not have a shortage of things to sell. I have the opposite problem.

I have built products for workflow automation, public-contract intelligence, sales research, sports data, lesson planning, creator protection, media, and several smaller utilities. Some are working applications. Some have payment infrastructure. Some are polished experiments with no real distribution.

I finally stopped asking, “Which new product should I build?”

The new question is, “Which three existing products deserve thirty focused days of selling?”

My rules for this first week:

1. No new products.
2. Every active offer needs one specific buyer.
3. Every offer needs one painful problem that can be explained without saying “AI-powered.”
4. Every week must produce conversations, demos, purchases, or a clear reason to kill the offer.
5. Building another feature does not count as distribution.

The three lanes I am testing are:

Workflow audits and automation builds for businesses with repetitive internal work.

Rebid Radar for regional companies selling technology into K-12 organizations.

Packaged AI systems that can be installed or adapted for a specific operation.

I will report what I actually do, what gets ignored, what creates conversations, and whether any of this converts into revenue.

The biggest risk is obvious: getting excited by another idea and escaping back into development. This post is partly an attempt to remove that emergency exit.

A lot of automation projects begin with someone saying, “We should add AI to this.”

That is usually too early.

Before I build an automation, I map five things:

The trigger: What event actually starts the work?

The handoffs: How many people, inboxes, spreadsheets, or systems touch it?

The judgment points: Which decisions require a human, and which are simply rules wearing a fake mustache?

The failure cost: What happens when a field is missing, a person forgets, or a system is unavailable?

The source of truth: Where should the final record live?

This tends to expose three different categories of work.

The first is deterministic work, such as copying data, creating records, sending standard notifications, and checking known conditions. Automate it normally.

The second is assisted judgment, such as summarizing documents, classifying requests, or preparing a recommendation. AI can help, but a person should approve the result.

The third is accountable judgment, such as hiring decisions, major financial approvals, or sensitive customer actions. The system should provide context, not quietly become the decision-maker.

The biggest mistake I see is automating the visible task while leaving the broken handoffs underneath it untouched. That creates a faster version of the same mess.

Disclosure: I run Flash AI Solutions and build Power Platform, custom workflow, and AI-assisted automation systems. This framework comes from the systems I use when scoping real builds. No product link here.

What is the most overcomplicated workflow you have seen someone attempt to automate?

I have spent the past year building a large collection of software projects, and I recently realized that the projects make more sense as a portfolio than as isolated startups.

The umbrella is Flash AI Solutions, an applied AI product studio.

A few examples:

Rebid Radar: finds public K-12 contract renewal and rebid signals for regional technology providers.

Flash Outreach: a human-approved research and outreach system that keeps evidence, contacts, campaign history, and replies connected.

Flash Props: a sports projection API and MCP interface, initially focused on competitive Call of Duty and other esports.

Chalkline: generates printable and interactive lesson activities from a teacher’s topic and difficulty requirements.

The shared engine is collecting difficult information, organizing it, and turning it into something operational.

My current challenge is not finding more products to build. That machine is working almost too well. The challenge is deciding which product has the clearest buyer and shortest route to a paying customer.

From the four examples above, which one can you understand fastest without additional explanation?

I am especially interested in whether the “applied AI product studio” positioning makes the portfolio feel coherent or whether it still sounds too broad.

At this point, I'll build something cool for free. I'm just really damn bored and wouldn't mind building some trust for the future. Anything software related, hit me up!

Hey everyone, I’m a developer offering affordable dev work for people who need something built, fixed, improved, or automated without paying agency prices. For as low as $10/hr

I can help with:

• Websites and landing pages
• Portfolio sites
• Business websites
• Web apps
• Mobile app fixes or planning
• Bug fixes
• UI/UX improvements
• Automation scripts
• AI tools and integrations
• API work
• Forms, dashboards, admin panels
• WordPress, React, JavaScript, HTML/CSS, Node, Python, and general dev help

I’m best for people who have an idea but don’t know how to build it, or already have something built that needs cleanup, fixes, redesign, or extra features.

Pricing depends on the job, but I’m keeping things budget-friendly. Small fixes can be cheap, and bigger builds can be discussed clearly upfront. No weird hidden fees.

Send me a DM with:

1. What you need built or fixed
2. Any links, screenshots, or examples
3. Your budget
4. Your deadline, if you have one

I’ll let you know honestly if I can do it, how long it should take, and what it would cost.

Open to one-off jobs, ongoing work, and quick fixes.

Thanks.