How Infiscroll Builds
Infiscroll runs every project through four stages (Discover, Design, Build and Grow) on a timeline set by the tier of build rather than by a promise. This page states how long each tier takes, what we need from you to hold that timeline, and what you own at the end.
The four stages
What happens in each stage?
Each stage ends with something you can see and sign off, so the project never moves forward on an assumption. The four run in order, and the next one starts when the last is approved.
Discover
Fixes the goals, the audience, the scope and the content you already have. Ends with a written scope and a fixed quote you approve before anything is designed. Keyword and “near me” research starts here, not after launch.
Design
Sets the structure in wireframes first, then the on-brand interface built to convert. Ends with screens you sign off, refined over the revision rounds your quote states. See website design.
Build
Turns the approved design into fast, accessible code with on-page SEO and schema written in rather than bolted on. Ends with QA across browsers and screen sizes before anything goes live. See web development.
Grow
Launches the site, connects analytics, and moves to the work that compounds: SEO, local search, ads and AI visibility. Ends nowhere: this is the stage that keeps running.
Seven steps, four stages
Where do the seven steps of web development fit into four stages?
The seven steps of web development (information gathering, planning, design, content, coding, testing and launch) are the same work Infiscroll runs as four stages, grouped by what you sign off rather than by what the team is doing that week. Published models split this work into anywhere from four to thirteen named steps, so the number of steps matters less than what ends each one.
The table below maps each of the seven steps onto the stage that owns it and names the sign-off that closes it.
| Seven-step model | Infiscroll stage | What closes it |
|---|---|---|
| Information gathering | Discover | An agreed scope and a fixed quote |
| Planning | Discover | The page map, with the keyword and “near me” research behind it |
| Design | Design | Wireframes first, then the screens you approve |
| Content | Design | The copy and images signed off page by page |
| Coding | Build | The built pages, with on-page SEO and schema written in |
| Testing | Build | The QA pass across browsers and screen sizes |
| Launch | Grow | The site live, analytics connected and the pages submitted for indexing |
Grow keeps running after launch, which is why the timeline below is quoted to launch rather than to the end of the engagement.
Timeline
How long does a website take to build?
A website takes two to ten weeks depending on the tier, because the tier decides how much has to be built rather than styled. A brochure site is assembled; a store with a checkout and a catalogue is engineered, and the difference shows up in weeks.
The four rows below pair each build with the timeline it typically runs to and the starting price it begins from. Both columns are the figures published on the pricing page, not estimates written for this one.
| Build | Typical timeline | Starting price |
|---|---|---|
| Static business site, up to 10 pages | 2–3 weeks | from ₹20,000 |
| Dynamic site with a CMS | 3–4 weeks | from ₹30,000 |
| Shopify or WooCommerce store | 4–6 weeks | from ₹30,000 |
| Custom store with its own workflows | 6–10 weeks | from ₹40,000 |
Every figure is a starting price for the scope beside it rather than a quote, and every timeline runs from the day content and access arrive, not from the day the quote is signed. That distinction is the single biggest cause of a project running late, which is what the next section is about.
Your side
What does Infiscroll need from you?
Three things set the pace: content, feedback and access. Almost every project that runs late runs late on one of them, and none of the three is something a studio can supply on your behalf.
Content means the text, images, logo and product or service details that fill the pages. A design can be built around placeholder text once; it cannot be finished around it. Feedback means a decision at each sign-off point, ideally from whoever has the final say, because a review that collects three opinions and no decision costs more time than it saves. Access means the domain, the hosting and any existing accounts, often the slowest item of the three, because it sits with a person who registered something years ago.
Where material delay comes from the client side, the timeline moves with it. That is stated plainly in our terms rather than raised as a surprise mid-project. You are also responsible for the accuracy of the content you supply and for holding the rights to any text, images or trademarks you hand over: a point worth checking before stock images go on a commercial site.
None of this needs to be ready before you get in touch. Discover exists precisely to work out what you have and what is missing.
Handover
What do you own when it is handed over?
You own the design files, the website content and the custom code written for you, once the project is paid in full. Infiscroll keeps its own pre-existing tools, libraries and internal frameworks and grants you a perpetual licence to use them inside your deliverable; third-party components stay under their own licences.
Ownership of commissioned work moves by written agreement rather than automatically on payment, which is why it belongs in the quote rather than in a conversation. The statutory reason, and what to ask any studio for, is set out on the services page, and the clause itself is in our terms.
After launch
What happens after launch?
On launch day the site goes live, analytics and Search Console are connected, and the pages are submitted for indexing, so performance is watched from the first week rather than assumed. Launch is the start of the Grow stage, not the end of the project.
Every project includes a one to two month support window after launch, as published on our pricing page. Breakages inside that window are fixed as part of the build, not billed as maintenance.
What comes next is a choice rather than an automatic bill. Recurring work (SEO, local SEO, AEO and GEO, and paid campaigns) runs as a separate monthly engagement, billed monthly in advance, and either side may end it on 30 days’ written notice. Nothing is bundled invisibly into a build price and nothing locks you in.
A site left alone still works; it just stops improving. Search results move, competitors publish, and the pages that earned traffic in month one need maintaining to keep it.
FAQ
Our process: questions answered
Eight questions come up on almost every discovery call: how many stages a build takes, how long it takes, how involved you need to be, what delays a project, what we need to start, how revisions work, what happens after launch, and whether rankings are guaranteed. The answers below are the same ones we give on the call.
How many stages does a website build actually take?
Infiscroll runs four stages (Discover, Design, Build and Grow) covering the same seven steps other models name separately: information gathering and planning sit in Discover, design and content in Design, coding and testing in Build, and launch opens Grow. Published models split the work into anywhere from four to thirteen steps, so what ends each stage matters more than how many there are.
How long does the whole process take?
It depends on the tier: about 2–3 weeks for a static business site, 3–4 for a dynamic site with a CMS, 4–6 for a Shopify or WooCommerce store, and 6–10 for a custom store. Apps and custom software are quoted per project. Every timeline runs from the day content and access arrive.
How involved do I need to be?
Mostly at Discover and at each sign-off point. Three things set the pace, content, feedback and access (and a decision from whoever has the final say keeps a review from turning into a delay.
What delays a website project?
Three things set the pace) content, feedback and access. Where material delay comes from the client side the timeline moves with it, which is what Infiscroll's terms state; every quoted timeline runs from the day content and access arrive rather than from the day the quote is signed.
What do you need from me to start?
Your business details, what the site has to achieve, any branding or content you already have, and a short discovery call. Nothing needs to be finished before you get in touch.
How many revisions are included?
Each quote states its own revision rounds. Revisions refine the agreed scope; a change to the scope itself is quoted before the work starts rather than invoiced after it.
What happens after launch?
The site goes live, analytics and Search Console are connected, and the pages are submitted for indexing. Every project includes a one to two month support window after launch, as published on our pricing page, so breakages in that period are fixed as part of the build. Ongoing SEO, local SEO, AEO/GEO and ads run as a separate monthly engagement, billed monthly in advance, endable by either side on 30 days' written notice.
Do you guarantee a Google ranking?
No. Infiscroll guarantees the work, not the market: rankings, traffic and conversions depend on search engines and competitors outside anyone’s control. What is committed is the scope, the method and the reporting in your quote.
Ready to start?
Two things make a first message useful: what the business does, and what the site has to achieve. With those, Discover starts from something concrete instead of a blank page.
Start your project