Phillip Karaya | Build With Phil

10+ years building businesses. Now I turn the lessons into AI tools, automations and systems you can use. Free guides + weekly builds ↓

[Phillip Karaya | Build With Phil @buildwithphilai]

Start✅, learn 🧠, fail❌….SCALE 🚀

[Phillip Karaya | Build With Phil @buildwithphilai]

Went quiet in my own community for a week once. Came back and people had shipped stuff without me.
That’s why “AI That Makes Cents” stays free — builders helping builders.
Door’s open → https://t.co/LgcTqmPlaN

[Phillip Karaya | Build With Phil @buildwithphilai]

True story: I taught the inbox system out loud so many times I finally wrote it down ($47).
Same bones as the free version — just tighter, repeatable, in your voice.
Start free or grab the pack: https://t.co/LgcTqmPT0l

[Phillip Karaya | Build With Phil @buildwithphilai]

Saturday morning used to mean catching up on Marketplace “still available?” threads from Friday night.
Ugly. Slow. Lost deals.
I started documenting the free DIY path so I wasn’t the only one stuck in that loop.
→ https://t.co/LgcTqmPlaN

[Phillip Karaya | Build With Phil @buildwithphilai]

@Tesla_Optimus_K Cute agents asking for email + messages + cards is the permission creep I refused on Marketplace. Wide-open access on a seller account is how a helpful bot leaks. Draft-only, human send.

[Phillip Karaya | Build With Phil @buildwithphilai]

@AIVibecode More tokens didn’t mean better Marketplace drafts — overnight regenerations got longer and more formal. I capped loops and scored leakage instead of burning context for a “richer” yes.

[Phillip Karaya | Build With Phil @buildwithphilai]

@null_founder Treating internals like a stable API is how I glued the drafter to a fragile path that broke overnight. I owned the gate in my harness instead — model can change, address/price rules don’t.

[Phillip Karaya | Build With Phil @buildwithphilai]

@4A4556494C Injection into the reply workflow is why excess tools had to go. If a prompt can hitch a ride, it shouldn’t find calendar + address book waiting. Fewer tools, human still on send.

[Phillip Karaya | Build With Phil @buildwithphilai]

@amn_baluni Human review felt like the cost I wanted to delete. Then a blind send taught me the review cycle is the product. Latency dropped; I kept preview-before-send on purpose.

[Phillip Karaya | Build With Phil @buildwithphilai]

@arta_asd @nazkhatoonm9 Architecture diagrams didn’t catch a workflow that auto-accepted a lowball. Use-case design for me starts with which step stays human: address, price, meetup. The rest can be agentic.

[Phillip Karaya | Build With Phil @buildwithphilai]

@aicashboss Click costs are the wrong first metric if the side hustle is inbox drafts. I burned time on ads before the product could hold a price floor. Fix the gate, then worry about acquisition.

[Phillip Karaya | Build With Phil @buildwithphilai]

@willlinprod Beginner-friendly and free is the bar I missed when early docs assumed Claude Code fluency. Community + free DIY for a draft queue without the engineering tax: https://t.co/LgcTqmPlaN

[Phillip Karaya | Build With Phil @buildwithphilai]

@swif_ai Symlink escape is the filesystem version of what hit our reply flow: believed sandbox, still reached the address book. I treat “can it see X?” as the product question, not the brochure.

[Phillip Karaya | Build With Phil @buildwithphilai]

@74th Private VPC sandbox is real safety for code. For Marketplace replies the leak was still a sentence inside the box. Network isolation doesn’t replace preview-before-send on buyer text.

[Phillip Karaya | Build With Phil @buildwithphilai]

@treyvijay Roadmaps don’t survive first contact with someone else’s listings. Demo works on mine; on theirs the voice is wrong and the price rule is missing. Implementation in real threads is the job.

[Phillip Karaya | Build With Phil @buildwithphilai]

@Nodepaid0r A registry of independent agents makes me want clearer IDs on the other side of Marketplace too. If I can’t tell bot from buyer, the drafter stays strict — no price moves without me.

[Phillip Karaya | Build With Phil @buildwithphilai]

@HackersAgents Audit logs showed a draft that almost sent with a cross street. Secrets and env boundaries weren’t enough; I needed a log line for “blocked meetup phrase” before preview-before-send.

[Phillip Karaya | Build With Phil @buildwithphilai]

@unclebobmartin @abdel_ramadhan Vibe-coded the first reply agent in a weekend. Clean code wasn’t the miss — missing tests for “did it offer a meetup” was. Engineering the constraint mattered more than the demo speed.

[Phillip Karaya | Build With Phil @buildwithphilai]

@tuTransform Swapping providers broke our voice overnight — new model, same repo, drafts got skippy and dropped the ask-me-before-price branch. Provider sits behind the checks or it’s a faster bug.

[Phillip Karaya | Build With Phil @buildwithphilai]

@Shashikant86 @zeddotdev @jetbrains @opencode @kirodotdev One protocol across agents is useful until Marketplace rules don’t travel with the session. I put price/address/meetup denies in the shared mod layer so ACP hops don’t drop the gate.

[Phillip Karaya | Build With Phil @buildwithphilai]

@anvanvan @chang_defi Agents driving devices is the scary version of agents driving my inbox. One test “drove” a send. Device control stays behind a preview I approve — same as reply text before it hits a buyer phone.