ProWorkSpace.

Freelancers spend most of their week not earning.

Upwork's economics punish volume. A freelancer with a $50 hourly rate who takes two hours per proposal and converts at 5% is losing their margin before the first invoice. The best proposals are researched, tailored, and concise — three properties that don't scale with copy-paste templates or generic AI wrappers.

I'd watched this for years while helping freelancers rank their profiles on Google. The ranking got them traffic. The proposal wall killed the conversion. So I built ProWorkSpace — a Chrome extension that lives on the Upwork job page, reads the brief, and drafts a proposal the freelancer can approve or edit in seconds.

Draft in the page. Ship in the page.

Every competing tool I tried was an external app — open a tab, paste the brief, copy the output, paste it back. That loop kills the time saving. I wanted the AI to live inside the Upwork UI so the friction was zero.

So ProWorkSpace ships as four things, each one responsible for a different friction point in the freelancer's day:

• A Chrome extension that injects an AI panel into the Upwork cover-letter modal, watches for the brief, and drafts a proposal styled to the freelancer's profile.
• A marketing site with an activation flow that explains the value in 30 seconds and turns a skeptical first-time visitor into a trialed user.
• A Stripe-backed billing layer that handles subscription conversion, plan tiers, and payment recovery without a finance team in the loop.
• An admin panel that lets me gate features, monitor usage, and push prompt updates without shipping a new extension build.

The whole thing had to look, move, and behave like it was built by a ten-person team. Shipping it solo meant every decision had to compound.

The pieces that aren't obvious from the screenshots.

Most Chrome extensions fail on the same three invisible problems. Getting these right was half the battle.

• SPA safety. Upwork re-renders chunks of its page without triggering a full navigation event. The naive "run on load" injection misses 80% of page states. The extension uses a MutationObserver gated by a dataset flag so it injects exactly once, per visible job posting, even as Upwork re-mounts the surrounding React tree.
• Prompt versioning. The AI drafts are only as good as the latest prompt. Ship that prompt inside the extension and every iteration costs a new Chrome Web Store review. So the extension pulls the active prompt ID at runtime from the API, and the admin panel lets me swap prompts in seconds.
• Deliverability of the marketing funnel. SaaS acquisition costs break the math for small-ticket products unless you control the full funnel. I built landing, Stripe, and admin as one coherent stack so the cost of iterating on any of them is minutes, not days.

Why this matters on a CV.

Most freelance marketers can talk about what a good funnel looks like. Most extension developers can ship a Chrome extension. What's unusual is building both, gluing them together with payments, and operating the result as a live product for real paying customers — as a single person, in a few months.

ProWorkSpace is the proof case for my positioning: one operator replaces the three-vendor stack. The SEO lead, the developer, the billing engineer — one brain, coordinated delivery, no handoffs, no communication tax.