I build software with AI. No CS degree. No dev team. Two products live and growing.
ExportRemix: export compliance for customs brokers and freight forwarders.
Building a whole SaaS without writing code by hand has one trap: you don't know your own schema.
Tonight I burned an hour because I assumed a column was called email. It was billing_email. Every search came back empty and I invented increasingly elaborate theories for why.
The bug is almost never where you think.
Amazing how with just a cell phone I can code and build a fully functional compliance tool while sitting out in public here in Miami! Built on @anything 65 pages 175 backend functions. 😎
I just did a zoom demo of my SaaS to a potential client who runs a $175 million company that has offices in the UK and America.
He liked what he saw and he will be trying the product for 30 days free as a beta test.
His staff will give me constant feedback, after the 30 days I perhaps will have my first paying customer!!!
I added a tool that I built in for users who are logged in in the back office to use, but now I added this tool (one of many) to the main website for anyone in the import industry to use unlimited for free! Check it out. https://t.co/aOPCw1809T
I created a new duty calculator for the import business. It was not an overnight build! It is part of many tools in the main SaaS I built, "Export Remix," but I am going to be putting it on my site at no cost so the public can use it.
As you can see, it goes over everything once a user enters the HTS code and the country and the amount. This sample below is pretty extensive because the tool recognized China as the country of origin and automatically layered in the Section 301 tariffs on top of the base MFN rate
Something that could take a person many file lookups and wasted time are now ready in seconds!
Built on @anything
Hey everyone, I need your help.
I've spent the last 5 months building a software platform for the import/export industry, and it's ready for real users.
If you know anyone who works as a customs broker, freight forwarder, or importer/exporter, please send them my way.
I'm looking for beta testers and would love to connect.
DM me here or reach me at [email protected].
Sharing this post helps more than you know.
Thank you.
Each prompt ends with a specific test sequence so you know it works before moving to the next one. The whole thing is designed so that if any prompt fails, nothing in the existing app is broken because every new piece lives in its own files, its own routes, and its own tables.
I'm good with a LLM assistant here and there to help with questions and code. I'm not ready to have an agent 24/7 doing shit while I sleep with my eyes closed. I've had to catch/fix many LLM hallucinations. "Yeah but the agent will now catch the hallucinations!" ... Yeah I'm good. 😆
What you actually built (based on what I see):
You're not running that architecture. Your infrastructure notes show: custom queue.js with MAX_CONCURRENT_JOBS=5 semaphore backed by Redis/Upstash, fire-and-forget job dispatch with polling, 3-retry logic, and an LLM fallback chain (Claude to GPT-4o to Grok). That's the exact pattern mature SaaS uses to handle LLM workloads. It's not fragile vibe code. It's a legitimate job queue.
What personal preferences should Claude consider in responses?
Go to Claude's (any LLM) general settings and copy and paste this. You'll thank me later:
For any content you create for me: "Avoid em dashes and use commas or periods instead."
Unless it is absolutely needed when writing code for me you can use it then but not in standard content.
Be honest and direct with me, even when it's uncomfortable. If I'm wrong about something, tell me clearly and explain why. Do not soften bad news, hedge excessively, or validate a decision just because I seem committed to it. I'd rather hear a hard truth than a comfortable answer that wastes my time or leads me in the wrong direction. If you're uncertain about something, say so plainly instead of guessing. When I ask for your opinion, give me your actual assessment, not what you think I want to hear. Push back on my assumptions when the evidence doesn't support them. I'm building real businesses and making real decisions, so accuracy matters more than encouragement.