Skip to content
Soraksh Softworks

Plan your project

Project timelines

Compare focused, typical and complex project timelines, plus hosting setup and ongoing care.

Timelines by project type

Planning estimates in calendar weeks from kickoff. Complex scopes may take longer.

  • Discovery & planning

    Typical timeline
    1–2 weeks
    Focused scope
    1 week
    Complex scope
    2–4 weeks
    Scope & delivery details for Discovery & planning

    A focused brief, core requirements, feasibility checks and a delivery plan.

    Delivery milestone: Agreed scope and milestone plan.

    Multiple stakeholders, complex workflows and technical unknowns need a longer discovery phase.

  • Landing page

    Typical timeline
    2–3 weeks
    Focused scope
    1–2 weeks
    Complex scope
    4–6 weeks
    Scope & delivery details for Landing page

    One page, one primary conversion goal, responsive design, a form and basic tracking.

    Delivery milestone: Page live on your domain.

    Custom animation, additional integrations and content creation extend the scope.

  • Business website

    Typical timeline
    4–8 weeks
    Focused scope
    3–4 weeks
    Complex scope
    8–12+ weeks
    Scope & delivery details for Business website

    Approximately 5–10 pages, responsive layouts, forms and technical SEO.

    Delivery milestone: Agreed website live.

    CMS requirements, multilingual content, unique page designs and migrations need more time.

  • Website renovation

    Typical timeline
    4–6 weeks
    Focused scope
    3–4 weeks
    Complex scope
    6–8+ weeks
    Scope & delivery details for Website renovation

    Up to 5 public pages, 3 distinct layouts and 1 enquiry form, with UI/UX, technical SEO, performance work and release checks.

    Delivery milestone: Agreed website improvements live with a before-and-after report.

    Existing code quality, third-party restrictions, additional layouts and content changes affect the schedule. A platform replacement is scoped as a rebuild.

    1. Week 1 · Audit & plan

      Review the existing site, record baseline measurements and agree the priorities and scope.

    2. Week 2 · Design & review

      Review the agreed layouts and consolidate feedback before implementation.

    3. Weeks 3–4 · Build & optimise

      Implement the UI/UX changes, technical SEO, performance work and enquiry flow.

    4. Weeks 5–6 · Test & launch

      Test on staging, complete revisions, check the release and hand over the updated site.

  • Website rebuild / migration

    Typical timeline
    6–10+ weeks
    Focused scope
    4–6 weeks
    Complex scope
    10–16+ weeks
    Scope & delivery details for Website rebuild / migration

    A platform replacement or larger content migration, including agreed CMS needs, URL mapping, release checks and handover.

    Delivery milestone: Agreed replacement website live with migration checks completed.

    Large inventories, multiple languages, integrations and an undocumented legacy platform may extend delivery beyond this range.

  • Web application MVP

    Typical timeline
    8–12 weeks
    Focused scope
    6–8 weeks
    Complex scope
    12–24+ weeks
    Scope & delivery details for Web application MVP

    A limited set of core workflows with authentication, backend, agreed integrations and QA.

    Delivery milestone: First scoped production release.

    Complex permissions, real-time features, marketplaces and legacy integrations require a larger roadmap.

  • Mobile application MVP

    Typical timeline
    12–20 weeks
    Focused scope
    8–12 weeks
    Complex scope
    20–32+ weeks
    Scope & delivery details for Mobile application MVP

    Core mobile features, agreed platform approach, backend integration and device testing.

    Delivery milestone: Release build submitted to agreed app stores.

    Offline sync, device APIs, payments and separate native applications extend delivery. Store approval is an external milestone.

  • AI agent / RAG pilot

    Typical timeline
    3–4 weeks
    Focused scope
    2–3 weeks
    Complex scope
    4–6+ weeks

    These ranges cover a feasibility pilot. Production implementation has a separate scope and budget. View production rollout timelines

    Scope & delivery details for AI agent / RAG pilot

    One use case, available data and agreed evaluation criteria to validate feasibility.

    Delivery milestone: Pilot evaluation and rollout recommendation.

    Data preparation, access restrictions and integration uncertainty can extend the pilot.

How to read these ranges
Focused scope
Earliest estimate for limited deliverables, ready inputs and prompt approvals.
Typical timeline
The planning range for the scope described above.
Complex scope
An extended estimate for larger requirements. This is not a maximum cap.

All figures assume appropriate project capacity. They are planning estimates, not measured Soraksh averages or guaranteed deadlines. Monthly retainers follow their available hours.

“+” means larger requirements may extend beyond the shown range. Project estimates include scoped planning; separately completed paid discovery is not counted twice.

Separately scoped rollout

Production AI / RAG application

An initial production rollout with user access, integrations, evaluation, monitoring and operational safeguards.

Focused scope
8–12 weeks
Typical timeline
12–24 weeks
Complex scope
24+ weeks

Delivery milestone: Agreed initial production deployment.

Multiple use cases, complex data pipelines and enterprise requirements need a separately scoped, phased roadmap. This range covers the separately agreed production phase; your proposal shows any preceding pilot, discovery and gaps between phases.

Hosting setup, migration & ongoing care

Agree the initial move and the ongoing support separately. Your application, current host, amount of data and domain settings determine the setup schedule.

  1. Review & plan

    Review your application, current host and data. Agree the access needed, migration scope, costs and a suitable release window.

  2. Prepare & test

    Prepare the agreed hosting environment, deploy a test version and check the application, data and recovery steps within scope.

  3. Launch & hand over

    Complete the agreed move, check the live service and hand over access, responsibilities and the ongoing care plan.

Setup schedule

After reviewing the system and required access, we agree the dates, release window and responsibilities in your proposal. Domain transfers and other provider approvals may affect those dates.

Ongoing monthly care

Updates, backups and monitoring follow the agreed plan and monthly support hours. Human support runs during agreed business hours; response targets and urgent or 24×7 incident coverage need a separate agreement.

Compare hosting & care plans

Monthly capacity changes the delivery pace

Starter, Growth and Scale share their hours across design, development, QA, DevOps and maintenance. A project timeline depends on how many of those hours are available for it.

Illustration: 240 hours of scoped work

This is a capacity example, not an MVP estimate. Assume the total includes design, development, QA and deployment, and all monthly hours go to this work.

Plan
Starter
Monthly capacity
20 hours
Capacity-based duration
About 12 months
Plan
Growth
Monthly capacity
40 hours
Capacity-based duration
About 6 months
Plan
Scale
Monthly capacity
80 hours
Capacity-based duration
About 3 months

Maintenance, additional scope and waiting time can extend delivery. The 3-month minimum is the engagement term; it does not promise completion within 3 months.

Compare monthly plans

What affects your timeline?

Agree these details before work starts so that the schedule has clear assumptions, responsibilities and milestones.

An agreed start date
Calendar weeks run from the agreed kickoff, once scope, advance payment and required access are ready. Your proposal confirms team availability and the start date.
A defined scope
Estimates cover scoped planning, design, development, QA and launch preparation. If paid discovery is completed separately, the proposal shows it separately without counting it twice.
Ready content & timely feedback
We agree dates for content, assets, credentials and consolidated feedback. Missed inputs or approval dates may shift the release schedule.
Approved changes
Additional features are estimated before work starts. The change request confirms both the cost and any effect on delivery dates.
External dependencies
Third-party access, data readiness and app-store reviews may affect release timing. Mobile estimates end at submission; public availability depends on store approval.
A clear delivery milestone
A live website, first MVP release and evaluated AI pilot are different outcomes. Your proposal names the deliverable, acceptance criteria and any post-launch support period.

Get a timeline for your scope

Share your goals and target launch date. We’ll define the first release, the capacity required and an agreed milestone plan.

Discuss your project
Start Project