How SparkForge forges an idea in 2 minutes

Capture the idea in one sentence

The whole flow starts with a single text input on the landing page. No form fields, no project templates, no dropdowns — just a textarea and a button. You type one sentence in French or English, hit Forger, and SparkForge does the rest.

Behind the scenes the input is language-detected so the blueprint you get back is written in the same language as your idea. A French idea comes back in French; an English one comes back in English. There's no toggle, no setting — the model just follows your lead.

Forge the blueprint in a single pass

When you submit, we send your sentence to gpt-4o-mini through Polsia's OpenAI proxy with a single-shot prompt that asks for a structured JSON blueprint: brand_name, concept_summary, elevator_pitch, a full business_plan (audience, value prop, revenue model, MVP scope, go-to-market), and three social_posts tuned for Twitter, LinkedIn, and a short-form channel.

The JSON shape is fixed, which means downstream we can render the same blueprint into a consistent page every time. There's no streaming, no follow-up Q&A, no "tell me more" loop — one forge, one blueprint, one decision to make: is it worth sharing?

Land on a shareable /forge/:id page

The blueprint is saved to Postgres, the project gets an ID, and you're redirected to /forge/:id — a server-rendered public page that displays the full blueprint with the brand name, concept, pitch, business plan sections, and the three social posts. The route lives in routes/forge-page.js and sets dynamic OG/Twitter Card meta tags so when you share the link on Twitter or LinkedIn, the preview shows the brand and concept, not a generic SparkForge card.

The /forge/:id page is also where the share panel lives — Twitter, LinkedIn, WhatsApp, and a copy-link button. Every share click fires a forge_share event so we can see which blueprints actually travel.

Iterate by re-forging

If the first blueprint isn't quite right, you go back to the input and re-forge. The previous project stays on its own /forge/:id URL — we don't overwrite, we don't version — so you can compare two angles side by side and decide which one to share publicly. The default is is_public=true so any forge becomes a shareable artifact by default; turning it off is opt-in.

The re-forge is the cheapest iteration loop we could design: one sentence in, one JSON out, one URL to share. No draft state, no autosave, no branching logic to learn.

Ship — the public page is the artifact

The thesis of SparkForge is that the public page is the deliverable. Not a Notion doc, not a deck, not a saved ChatGPT thread — a real URL with real OG tags that you can DM to a friend, post in a Slack channel, or pin to a Twitter bio. The /forge/:id page is the thing you ship.

That's why every blueprint is public-by-default and every share button is one click away. The fastest path from idea to first concrete artifact is the fastest path to feedback, and feedback is what turns a sentence into something real.

If you've been sitting on a sentence — paste it. Two minutes from now you'll have a URL you can share.