Skip to content
Our process

Eight weeks, six steps, nothing hidden

You see a staging URL in week one and a live changelog throughout. Here is exactly what happens, when, and what we need from you at each point.

  1. 01

    Discover

    Week 1

    We audit what you have, interview the people who talk to your customers, and pull the numbers. You get a written diagnosis before anyone opens a design file.

    You receive

    • Analytics and technical audit
    • Customer and stakeholder interviews
    • Opportunity sizing

  2. 02

    Strategy

    Week 2

    We agree on one metric that matters and the shortest route to moving it. Scope, sequence, and success criteria are signed off together — no surprises in week six.

    You receive

    • Growth model and target metric
    • Scope and roadmap
    • Success criteria

  3. 03

    Design

    Weeks 3-4

    Wireframes first, then a design system built from real content. Every screen is reviewed against the metric it is meant to move, not against taste.

    You receive

    • Wireframes and user flows
    • Design system in Figma
    • Content model

  4. 04

    Build

    Weeks 5-7

    Next.js on the front, Node.js behind it. You watch it come together on a staging URL from day one, with weekly demos and a live changelog.

    You receive

    • Staging environment from day one
    • Weekly demos
    • Automated tests and CI

  5. 05

    Launch

    Week 8

    Redirects mapped, schema validated, analytics firing, Core Web Vitals green. We stay on the call through the DNS switch and the first traffic.

    You receive

    • Redirect and SEO migration plan
    • Performance and accessibility pass
    • Team handover session

  6. 06

    Grow

    Ongoing

    Launch is the start of the measurement. We run experiments in two-week cycles and report on the same dashboard your leadership already reads.

    You receive

    • Fortnightly experiment cycles
    • Monthly performance report
    • Quarterly roadmap review
What we need from you

Three things that decide whether we ship on time

Projects rarely slip because of engineering. They slip because of these.

  • One decision-maker

    Someone who can approve a wireframe without convening a committee. Reviews by committee add two weeks, every time.

  • Content, early

    Copy, photography and product data in week two rather than week six. Projects with content ready ship two weeks faster on average.

  • Access, on day one

    Analytics, Search Console, DNS and hosting. We cannot baseline what we cannot see, and the audit is what everything else is built on.

Questions

Answered before
you have to ask

Pricing, timelines, ownership and what happens if it does not work. If yours is not here, ask it directly.

Ask us anything

What does a project cost?

Marketing sites start at $4,500 and most land between $6,000 and $15,000 depending on page count and integrations. Custom software starts at $6,000. Retainers begin at $1,200 a month. Every proposal is fixed-scope and fixed-price, so the number you approve is the number you pay.

How long does a website take?

Five to eight weeks for a marketing site, nine to twelve for a platform or storefront. The single biggest variable is content — projects where copy and photography are ready ship two weeks faster on average.

Do you work with businesses outside Nepal?

Around half our clients are overseas, mostly in Australia, the UK, and the Gulf. We keep a four-hour overlap with your working day and run every project asynchronously in writing, so timezone is a scheduling detail rather than a risk.

Who owns the code and the accounts?

You do, without exception. Repositories sit in your organisation, hosting and ad accounts are billed to you, and design files are licensed to you outright. There is no lock-in and nothing to buy back if you leave.

Will the new site hurt our existing rankings?

Not if the migration is done properly. We crawl the current site, map every URL to its replacement, ship 301 redirects, and monitor Search Console daily for the first month. Most of our migrations gain organic traffic within six weeks.

What happens after launch?

Thirty days of support are included with every build — bugs, tweaks, and questions. After that you can take a growth retainer, buy support hours as needed, or run it yourself with the documentation we hand over. All three are genuinely fine.

Why is the company called nlogn?

It is the complexity of an efficient sort — O(n log n). Add more input and the cost grows, but far slower than the output. That is the shape of growth we build for: compounding, not linear.

Week one starts whenever you do.

Tell us the number you need to move. We will come back within one working day with an honest read on whether we can move it — and what it would take.

Start a projector email nlognweb@gmail.com
  • A written diagnosis before any proposal
  • Fixed scope, fixed price, no change-order games
  • You own the code, accounts and design files