Will Ness

what were you using before?

How do pros write CSS?

AI

What's the book?

If you made it far, please follow for more posts like this :)

10. Audit Trail Summarizer
- description: Converts system logs into readable summaries for auditors.
- technical skill required: 5/10
- estimated market size: $1.2B

9. KYC/AML Document Validator
- description: Validates customer docs and flags suspicious data or patterns.
- technical skill required: 7/10
- estimated market size: $5B

8. Automated ESG Report Writer
- description: Converts internal metrics and docs into ESG-compliant reports.
- technical skill required: 6/10
- estimated market size: $2.5B

7. Audit Prep Interview Assistant
- description: Simulates audit interviews to train employees using policy docs.
- technical skill required: 4/10
- estimated market size: $1B

6. LLM-Powered Evidence Organizer
- description: Auto-tags and organizes audit evidence by linking it to controls.
- technical skill required: 6/10
- estimated market size: $1.5B

5. Regulation Diff Tracker
- description: Tracks legal changes and auto-compares against internal policies.
- technical skill required: 5/10
- estimated market size: $2B

4. Smart Audit Sampling Engine
- description: Finds anomalies and suggests optimal samples from full datasets.
- technical skill required: 6/10
- estimated market size: $3B

3. Email & Chat Compliance Scanner
- description: Flags policy violations in internal comms via browser extension or API.
- technical skill required: 5/10
- estimated market size: $4B

2. Continuous Document Auditor
- description: Monitors internal files in real-time for compliance issues using LLMs.
- technical skill required: 7/10
- estimated market size: $6B

1. AI-Powered Policy Checker
- description: Scans corporate policies for gaps or violations against GDPR/AML/ESG standards.
- technical skill required: 6/10
- estimated market size: $5B

Start building what millions actually need.

Check out these Y Combinator inspired business ideas that any solopreneur can build in within a few months.

See thread below 👇🧵 #buildinpublic

CoffeeChat Bot: Automated networking events for your Discord community | Product Hunt Keep your community alive and provide value via automated networking events in your Discord server. Automated scheduling, partner matching, and voice channel assignments.

I am launching my project CoffeeChat Bot right now on Product Hunt!

It's a tool to run automated networking events in any discord community.

Your support on my launch would really help me out:
www.producthunt.com/products/cof...

#buildinpublic

Come join a startup chat!

startupchats.willness.dev

The fastest way to learn is by talking to others who are facing the same problems you are.

#buildinpublic

Stop wasting time building unvalidated ideas

Use YC's Request For Startups (RFS) to go build solutions for problems handed to you by the titans of the tech industry.

Here are 10 example solutions for a RFS.

If you are still scouring reddit or twitter to find problems, you are wasting your time.

YCombinator's RFS (Request for Startups) has dozens of startup ideas

Here are 10 example headlines for a product that solves this Voice AI problem.

Go build!

is basically the same, except for me spinning up dev tools quicker

Definitely!

Also, I forgot to answer your initial question of "how have you seen your workflows change?"

I'd say my overall workflows are really similar, I just spend more time writing prompts and reviewing code than I do actually writing code, and I can iterate quicker, but the overall process..

don't review the code at all, I just test it by running the script. I think this is fine for me because I don't want to overengineer small projects I build just to automate something or get work done quicker.

Depends on the use-case.

For production code in large repositories, I review every single line of code manually. Sometimes I make small manual changes to fix things, or will reprompt for larger changes.

I have ended up building more 'internal tools' for myself using AI coding tools in which I...

My latest project Startup Coffee Chats has been live for 18 days now. 8 people have decided to take time out of their days to attend the events so far, for which I am super grateful.

Until attendance picks up, I am cutting down to 2 chats a week.

#buildinpublic

Until attendance picks up I decided to only run two chats per week. Do either of these work for you: Tuesday 9AM PST, Sunday 5PM PST?

L day so far

3d mockups for restaurantpassport.net are looking clleeeaaannn 👀👀

gonna get some advertisements out next

#buildinpublic

Day 15
2 participants

Total: 7 people
Goal: 50 people
Progress: ▓▓░░░░░░░░░ 14%

Day 14
4 participants

Total: 7 people
Goal: 50 people
Progress: ▓▓░░░░░░░░░ 14%

haven't posted daily updates in a few days, but we're starting to see 3-5 people show up per day :)

#buildinpublic