Start a Software Project Inquiry in English

Share your project scope in English.

Use this form if you want a reply in English. You can keep the scope rough. The goal is to understand your delivery lane, budget window, timeline, and decision blockers.

Website, product, platform, ERP, and AI workflow inquiries supported

Same backend lead pipeline as the Korean direct inquiry flow

Good for early scoping even if the spec is not finalized yet

Typical response Within 1 business day

Best fit for Scoping before vendor outreach

A laptop workspace on a meeting table, ready for a practical scope review.

A rough brief is enough if it is concrete. Photo by Headway on Unsplash

State the outcome

Lead with the product or workflow you need to launch.

Keep the brief rough

A full PRD is optional. Priority order matters more than polish.

Get a sharper reply

Add Loom, Figma, or quotes later if you want tighter feedback.

Fast scope brief

Get a sharper reply, faster

Start with the outcome, who needs it, and what phase one must include. Everything else can stay rough for now.

English response lane Only name, email, and phase-one scope are required.

What helps the most

Tell us what you are building, what phase one must launch with, and any hard deadline or budget guardrail. If your brief is rough, that is still enough to start.

What are you building? Lead with the outcome, not the tech stack. Work email Use the inbox where you want the scoped reply. Name What must ship in phase one? You do not need a full PRD. A rough phase-one brief is enough.

Add optional scope hints

Company Budget range Target timeline

Already have rough notes, a Loom, Figma, or a vendor quote? Mention that in the brief so we can reply more concretely. You can leave the optional hints folded if you want to move fast.