u/ibmi_dev

We build automated follow-up systems for HVAC shops, auto repair shops, and trades businesses. These are small business owners losing thousands per month because nobody follows up on their estimates or missed calls. We fix that with a done-for-you automation service.

The product works. We have a live demo, a clear ROI story, and a ready-to-sign contract. We need a closer to take warm leads and get them across the line.

This is a 100% remote, commission-only role. No base pay.

What you'll do:

Warm leads come in via email outreach (we run the outreach, you take the replies). You book a 20-30 minute Zoom call, walk the prospect through a live screen-share demo, handle objections, and close. We handle everything after the signature.

No cold calling. No list building. No admin.

What you'll earn:

• 25% of setup fee per close ($1,500-$2,500 setup = $375-$625 per deal)
• 10% of first 3 months retainer ($400-$800/mo = $120-$240 per deal)
• Average total per close: $620-$865
• Close 3/month: $1,860-$2,595. Close 5/month: $3,100+. Uncapped.

What we give you:

• A fully built interactive demo (you just walk through it on screen share)
• Warm leads via email (prospects have already shown interest)
• Objection handling guide for the 4 objections you'll always hear
• Contract template ready to send same day via PandaDoc
• Loom walkthrough of the full product so you know it cold

You're a fit if:

• You've closed B2B deals before, especially to small business owners
• You're comfortable running Zoom calls without a script
• You're in the US with a clear, professional phone presence
• You want commission income, not a salary

Bonus: experience selling to trades businesses (HVAC, plumbing, auto repair, roofing) or any service-based SMB.

Curious how shops actually handle audit journal review in practice.

A few questions:

1. Do you review it on a regular cadence, or mainly when an incident happens?

2. Any tools in use (Fortra, PowerTech, something homegrown), or is it manual?

3. Is there someone on your team who actually reads the output, or does it mostly sit there?

4. Any pain points worth knowing about?

Genuinely curious how common proactive review is vs. reactive.

Been using Claude and GPT-4o against IBM i code for the past year. Sharing what I've learned since most of what's out there is either vague or written by people who've clearly never seen an RPG program.

The single most important thing: models don't assume IBM i unless you tell them. If you just paste code cold you get garbage. You need explicit context every time.

For free-format RPG IV this works well:

>"I'm working with IBM i. This is free-format RPG IV. Explain what this program does, what external programs it calls, and what the key data structures represent. Don't explain basic RPG syntax, focus on the business function."

For fixed-format RPG/400 you also need to specify the column layout or the model misreads Factor 1, the operation, and Factor 2 pretty consistently.

What it's actually useful for: high-level program summaries, translating logic to plain English for business analysts, DB2 for i SQL, generating documentation headers for free-format programs.

Where it falls short: indicator logic (it notes them but rarely traces them correctly without the full program), multi-program call chains, anything where the business context isn't in the code.

The workflow that's been working for me: run the summary prompt, have someone who knows the codebase spend 15-20 minutes reviewing the output, then embed reviewed comments directly in source. A 200-300 line free-format program takes about 45 minutes end to end. Fixed-format takes longer because the review pass catches more.

Happy to share the specific prompts I use for free-format, fixed-format, CL, and DDS if anyone wants them.