// our process

Structured work that
delivers what we agreed to.

Four clear steps. Every UrgeSol project follows the same proven structure — Discovery, Planning, Build, and Support — so you always know where things stand and what comes next.

Discovery · Week 1
Planning · Week 1–2
Build · Week 2–8+
Support · Ongoing
// Step 01
01

Discovery — we start by listening.

Before anything is scoped, designed, or quoted, we take the time to genuinely understand your business. That means understanding your goals, your constraints, what has been tried before, and what success actually looks like in your context — not a generic template of success.

You start by filling in our project intake form. It takes around ten minutes and gives us the context we need to have a meaningful first conversation. We read every submission personally before responding.

Start your intake →
$ urgesol intake --new-project

discovery session:
business_goals → captured
target_audience → defined
existing_stack → reviewed
timeline → aligned
budget_parameters → confirmed

✓ all context gathered
→ moving to planning phase

What your proposal includes

Scope definition

Exactly what we will build, in clear non-technical language.

Technology recommendation

The stack we recommend and why it is the right choice for your situation.

Fixed project cost

A single number. Not a range, not an estimate — a firm quote.

Delivery timeline

Week-by-week milestones so you know what to expect and when.

Dependencies & risks

Anything you need to provide, and any factors that could affect the timeline.

Next steps

What happens immediately after you confirm, and who does what.

// Step 02
02

Planning — a proposal before a single line of code.

Within 24–48 hours of your intake, we send a written proposal — not a vague estimate, not a slide deck. A document that tells you exactly what we will build, what it will cost, and what the timeline looks like.

If the proposal is not right for your situation, we will tell you honestly — including recommending an alternative approach or a different provider if we genuinely believe that serves you better.

The proposal is yours to keep regardless of whether we work together.


// Step 03
03

Build — structured sprints, regular visibility.

We work in two-week sprints with regular check-ins. You see work in progress, give feedback before it is finished, and stay informed without needing to chase for updates. The quote is fixed — if our estimate was wrong, that is our problem to solve, not yours.

Everything is built in your environment, in your repository, with your credentials. There is no proprietary system that disappears if we stop working together.

Fixed quote · no surprises
Two-week sprint structure
Regular progress updates
Built in your environment
Thorough QA before delivery
Documented and handover-ready

Typical project timeline

1

Week 1–2

Environment setup, initial build, and first working version delivered for review.

2

Week 3–4

Feedback incorporated. Features refined, edge cases addressed, integrations connected.

3

Week 5–6

QA phase. Cross-device testing, performance checks, and security review.

4

Week 7–8

Final polish, documentation, staging deployment, and launch preparation.

5

Launch

Go live. Monitoring in place. Handover package delivered. Support begins if applicable.


$ urgesol handover --project client-platform

transferring repository access…
generating documentation…
packaging credentials vault…
scheduling walkthrough call…

handover package:
› full source code · your repository
› technical documentation
› admin and API credentials
› recorded walkthrough video
› optional: support retainer

full ownership transferred.
// Step 04
04

Support — you own it, we're here if you need us.

At handover, you receive the complete source code, all documentation, every credential, and a recorded walkthrough that covers how everything works. No dependency on us to keep your product running.

If you want ongoing support, updates, or continued development, we offer flexible retainer arrangements. But they are genuinely optional — not a way for us to hold your product hostage.

See support options →
// questions about the process

Things people ask before they start.

Timelines vary with scope. A focused single-service project typically runs 3–6 weeks. Larger platforms or multi-module builds may take 8–16 weeks. You will see the exact timeline in your proposal before anything is confirmed.
Not at all. We have worked with founders who have never written a line of code and with technical teams who want a reliable execution partner. We adapt our communication to what is useful for you, not what sounds impressive.
If a delay is on our side — estimation error, unforeseen complexity we should have caught — we absorb the time. If it is caused by something outside the agreed scope or by delayed inputs on your side, we discuss it transparently and agree on how to handle it before it becomes a problem.
Yes, completely. Everything produced during the engagement transfers to you at handover. We retain nothing, and there are no licensing arrangements that would restrict how you use or modify your own product.
Absolutely. Many of our clients return for additional phases, new features, or separate projects. If you want ongoing involvement, our retainer options cover everything from occasional maintenance to active continued development.
Quality issues are addressed as a matter of course — that is what the QA phase and feedback cycles are for. If something specific does not match what was agreed in the proposal, we fix it. We take what we sign up for seriously.
Yes. We regularly collaborate alongside internal developers, designers, or marketing teams. We integrate into your workflow rather than demanding you integrate into ours.
// next step

Ready to start the discovery phase?

Fill in the intake form — takes about ten minutes. We will review it personally and send a written proposal within 24–48 hours.