
ProcureX’s Next.js website. Construction software, eleven solutions, one AI layer.

Credits

Amit Pathania

Shreyash Chhatbar

Divyesh Vasani
Founded
2024
Location
Hyderabad, India
Company size
40+
Industry
Construction technology
Capabilities
Website
ProcureX makes software for construction and infrastructure teams. One platform covers planning and project controls, procurement and tenders, compliance and securities, and BIM-to-BoQ estimation, which turns a building information model (BIM) into a priced bill of quantities (BoQ). An AI layer called AI - IntelliSuite runs across all of it. The company was founded in 2024 and is based in Hyderabad, India, with an office in Oman.
ProcureX was one of our very first clients. We made its first website when Rango started, then its mobile app. This second website is made for its evolved, AI-first positioning.
Rango designed and built ProcureX’s new website in Next.js: 19 pages, from the homepage and the platform overview to a page for each of the 11 solutions. Amit Pathania and Shreyash Chhatbar designed it. Divyesh Vasani built it. It went live in November 2026.
The pages are long, and most of them move. On the homepage, a building under construction turns to glass as ProcureX’s AI scans it. An AI control tower catches a billing error and assigns the fix. On the BIM page, a model separates into the layers of an estimate. This case study walks through them page by page.
At a glance
Client: ProcureX, construction software for planning, procurement, compliance, BIM and AI, based in Hyderabad, India (founded 2024)
Relationship: one of our very first clients, with their first website, their mobile app and now this second website
Who the website is for: owners and CXOs, procurement heads, project and finance teams, BIM and planning leads, and site teams at construction and infrastructure companies
What we did: website design and a Next.js build: 19 pages, the motion and visuals on them, and a handover to ProcureX’s team
Design: Amit Pathania and Shreyash Chhatbar, in Figma
Development: Divyesh Vasani, in Next.js
Built with: Next.js 16, React 19, Tailwind CSS 4, GSAP, Lenis and Embla, with Paper shaders on the AI page
Live: since November 2026, at procurextech.com
The brief
One platform, many buyers.
This is our second website for ProcureX. Since the first one, its positioning has evolved to AI first, and the new website had to lead with that.
ProcureX runs a construction project from the first drawing to the last bill: schedules and progress, cost control, tenders and vendors, work orders and RA (running account) billing, bank guarantees and insurance, and quantities taken straight from BIM models. AI - IntelliSuite sits across all of it and flags what needs attention.
The people who buy it are just as varied. An owner wants the whole portfolio. A procurement head wants tenders and vendors. A BIM lead wants quantities they can defend. A finance team wants the bill to match the work.
The brief came down to four things:
Explain the platform, then each part. Show how it fits together before asking anyone to pick a module.
Show the product working. Most visitors have not seen ProcureX yet, so the website shows it in use instead of describing it.
Speak to every role and every kind of project, from data centres and hospitals to towers and townships.
Earn the trust of enterprise buyers. Owners and procurement heads judge a vendor by its website long before a demo.
Sort 11 solutions into three pillars
The menu mirrors how ProcureX sells.
ProcureX groups its product into three pillars: Plan & Control, Procure, and Comply & Secure. We built the navigation around them. Platform, BIM and AI - IntelliSuite each get their own page, and the Solutions menu opens on all three pillars, with every solution under its pillar and a one-line job beside it.
Plan & Control: construction planning, progress tracking, cost control and EVM, work orders and RA billing, and the project controls center
Procure: drawings to BoQ to tender, tender management, strategic sourcing, vendor intelligence and spend analytics
Comply & Secure: compliance and securities
Move across the menu and a soft highlight follows the pointer from item to item.
The Solutions menu: three pillars, eleven solutions, and a one-line job for each.
Open the homepage on the product at work
A building, scanned.
The homepage opens on one line: Everything Your Projects Run On, Made Intelligent. Beside it, a concrete building under construction turns to blue glass while ProcureX’s AI scans it. The module list opens, a red band marks the floor at risk, and the AI flags a cement stockout at Site C in one day. It suggests moving 600 bags from Site A, the risk is covered, and the finished building appears with the project back on track.
The sequence is one 23-second video that loops beside the headline.
The homepage hero: the AI scans a building, flags a cement stockout at Site C and covers it with 600 bags from Site A.
Explain the AI with one billing story
The AI control tower, in five steps.
Under the hero, ProcureX makes its main promise: reports tell you what happened, ProcureX tells you what’s next. Three words carry it: Detect, Explain, Recommend.
Then an example scene shows the promise on a real kind of problem. A weekly billing report comes in. ProcureX flags an RA bill where 187 sqm of internal plaster was claimed against 142 sqm measured on site. It explains why, names the vendor and the owner, and assigns an RA bill review to the QS (quantity surveying) team.
We coded this scene instead of playing a video. It stays sharp on any screen, its labels stay editable, and every word in it is text on the page, not pixels in a video.
A screen recording of the coded control tower: a billing report comes in, ProcureX flags an overclaim, explains it and assigns the review.
Give every module, role and project a way in
Three ways into the platform.
The next three sections answer the questions buyers bring. Which module do I need? What does it give someone in my role? Does it fit my kind of project?
Modules. A dark section lays out the three pillars as slides. Each slide lists its solutions beside the product on screen, playing in a loop.
Modules by pillar: each slide pairs its solutions with the product on screen.
Roles. One Source Of Truth steps through six roles, from owners and CXOs to site teams, with a photo and a short brief for each. A thin timer bar shows when it will move on, and a click jumps to any role.
Six roles, one platform: the section moves on by itself, or on a click.
Project types. Towers To Townships, One Platform slides six kinds of projects past as you scroll: Data Centers, Commercial & Office, Mixed-Use & Townships, Healthcare & Institutional, Industrial & Warehousing, and Residential & High-Rise.
Towers To Townships: the project types slide past as you scroll.
Give AI - IntelliSuite its own look
The AI page goes dark.
AI - IntelliSuite is ProcureX’s AI layer: one copilot that drafts, scores, explains and answers inside every part of the platform. Its page is the only fully dark page on the website, so the AI reads as its own layer the moment you land.
The hero is a sphere of dots that slowly shifts, rendered live in the browser with Paper’s open-source shaders.
AI - IntelliSuite: the one fully dark page, with a sphere rendered live in the browser.
Below it, eight copilots sit in a grid, from Ask IntelliSuite on every page to SmartTender, SmartSource, VendorIQ and SpendLens. Each card carries its own line drawing of the job it does.
One layer, eight copilots: each card has its own line drawing.
The named engines behind the copilots are drawn as a diagram we coded from the Figma design, so it stays crisp and its labels stay text. How It Fits then lays the AI over each pillar, one card at a time. Hover to pause it, or click to switch.
The named engines behind the copilots, coded from the Figma design.
How It Fits: the AI layer over each pillar, one card at a time.
Make BIM-to-BoQ the clearest page
From model to priced BoQ.
The BIM page explains ProcureX’s most technical product. It reads a design model or drawings, classifies the elements, measures them, and produces a priced BoQ grouped under IS 1200 or one of eight other published standards.
So it got the most visual work. The hero shows a building half in concrete and half in BIM wireframe, with a crane that slowly turns. Cards for clash detection, procurement inputs and quantity take-off are coded on top.
The BIM hero: a building half in BIM wireframe, with coded cards for clash detection, procurement inputs and quantity take-off.
Further down, the pipeline is an exploded stack of six layers, from upload to validation, that separate and settle as the section comes into view. It is coded from the Figma layers.
One governed pipeline: upload, classify, quantify, price, deliver and validate, as an exploded stack.
The page shows the inputs it takes: IFC and Revit models, DWG and PDF drawings, and federated or revised models, each on a dark card with a slice of the product.

Any format in, one BoQ out: a card for each kind of input.
The classification section turns the rule engine into four panels, one for each layer, also coded from the Figma layers.
Deterministic classification: four panels for the four layers of the rule engine.
Then come the standards it supports, IS 1200 and eight more for other regions, and four line drawings for how a rate gets built: take-off, rate build-up, cost checks and a model readiness gate.

IS 1200 and eight more: the published standards a BoQ can follow, by authority and region.

A priced BoQ with a defensible rate: four line drawings, four steps.
The page closes on the BIM Quantity Validator, set against a glass building and a blue sky.

The BIM Quantity Validator, set against a glass building and a blue sky.
Follow one quantity across the Platform page
The whole project on one page.
The Platform page is the overview. Its hero is a live diagram: Plan, Procure, Comply and Data/BIM around IntelliSuite, with pulses running along the lines as a drawing, a BoQ update and a vendor quote turn into one decision.
The Platform hero: drawings, BoQ updates and vendor quotes run through IntelliSuite to a decision.
Then the problem, in ProcureX’s own words: your project runs on 14 spreadsheets, 3 tools and a WhatsApp group. And the answer, as one thread. A quantity comes off the drawing and becomes a BoQ line, a tender, an award, a PO, an RA bill and, if it ever comes to it, an arbitration file. As you scroll, the section holds still and walks through each step.
From the drawing to the arbitration file: the section holds as you scroll and walks the thread.
Two dark sections close the page: how ProcureX works with the systems a company already runs, and how its AI keeps every action logged for audits.
Two dark sections: integrations with existing systems, and the audit trail behind the AI.
Build eleven solution pages from one template
Same story, different solution.
Every solution page follows the same order: a promise and a product view, proof, the features, everything the solution covers, the outcome, the copilot, why it works, questions, and links to the other solutions.
Each hero pairs a blue gradient with a photo from the work and the product’s own cards, so the eleven pages read as one set. Each solution’s content lives in its own data file, and the menu, the page routes and the sitemap read from the same list. A twelfth solution is a content change, not a new design.
Eleven solution pages, one template: each hero pairs a photo from the work with the product’s own cards.
Inside a solution page, construction planning: the features, the coverage list, the outcome and the copilot.
Show the company on About and Contact
About and contact.
The About page opens on a film of a tower under construction against a mountain backdrop, then the founder’s note, signed with a signature that writes itself as you scroll.
The About page hero: a tower under construction against a mountain backdrop.
The founder’s note: the signature writes itself as the section scrolls into view.
Four principles follow on a dark band, each with its own icon: defensible, global-ready, one system and human-approved. Then the leadership team and advisors, press coverage and open roles.

Four principles, each with its own icon.
The two offices, in Hyderabad and in Barka, Oman, are drawn as line art. The contact page puts the demo form next to ProcureX’s own promise: avoid delays and save 3-5% on cost.

Where To Find Us: each office drawn as line art.

Contact: the demo form, next to ProcureX’s own promise.
Close the homepage on a blueprint
The last screen and the footer.
The homepage ends on Plan It. Build It. Control It. A tower is drawn as a blue blueprint, and a band of the real photo sweeps up and down through it. Below, the footer sets PROCURE X in a pixel typeface across the full width.
Plan It. Build It. Control It.: a band of the real photo sweeps through a blueprint tower, then the pixel wordmark footer.
Rebuilt for phones
Not the desktop, shrunk.
The busiest visuals got their own phone versions. The Platform diagram is a separate, coded phone layout instead of a scaled-down image. The AI control tower stacks its cards, the BIM hero crops to a portrait version of the building, and the Platform stats sit two to a row.
On phones: the homepage, the Platform page and the BIM page.
Readable by search engines and AI assistants
Every page explains itself.
The build gives each page its own title, description, canonical address and share image. Structured data describes ProcureX as an organization and the website as a whole, solution pages carry breadcrumbs, and the sitemap is generated from the same list as the menu, so new solution pages are listed on their own.
The footer carries an “Ask AI for a summary” row: links to ChatGPT, Claude, Gemini (through Google’s AI Mode), Perplexity and Grok that open with a suggested prompt. It asks for a clear summary of ProcureX, its modules and who it is for, then offers to go deeper into a module or a demo.
The coded animations help here too. The words in the control tower, the engines diagram and the BIM panels are text on the page, not pixels in a video.

The footer: “Ask AI for a summary” opens five AI assistants with a suggested prompt about ProcureX.
Built AI-native
Figma for the design. Claude Code for the build.
Amit and Shreyash designed the website in Figma. We built it in Next.js with Claude Code, working from the Figma files, and used Codex to review the work, including a full pass on typography across the website.
Magnific made two of the BIM visuals: the glass building behind the validator, redrawn from a photo as a clean architectural render, and the motion in the BIM hero, generated from the still image.
AI tools did a lot of the typing. The design and engineering decisions stayed with our team.
Handed over, not held
ProcureX owns the code.
The code lives in ProcureX’s own repository, with a handover guide that covers running, building and deploying the website, editing content, and the conventions the code follows. ProcureX’s team deploys it on their own server.
Delivered: 19 pages, one shared template for 11 solutions, the motion on them, and a documented handover. We measure our work by how little our clients need us after launch.
Timeline
Live since November 2026.
The website went live on procurextech.com in November 2026. The coded control tower, the animated BIM visuals and a typography pass followed right after launch.
What construction software teams can take from this
Sort by job, not by module name. Three pillars made eleven solutions easy to scan, and every solution says its job in one line.
Show one real problem, start to finish. The control tower story takes 17 seconds and shows the product better than a feature list.
Code the motion that explains. Coded scenes stay sharp, keep their labels editable and keep their words as text.
Spend the most design time on the hardest idea. For ProcureX, that is going from a BIM model to a priced BoQ.
Give visitors a starting prompt. Footer links that open ChatGPT or Claude with a prompt about the product make it easy to ask an assistant for a summary.
Questions about this project
What did Rango do for ProcureX?
Rango designed and built ProcureX’s new website in Next.js: 19 pages covering the homepage, the platform, BIM, the AI layer, 11 solutions, the company, contact, and the privacy and terms pages, along with the motion and visuals on them. Amit Pathania and Shreyash Chhatbar designed it, and Divyesh Vasani built it.
How long has Rango worked with ProcureX?
Since Rango started. ProcureX was one of our very first clients: we made its first website, then its mobile app, and now this second website for its AI-first positioning.
What is ProcureX?
Construction software from Hyderabad, India, founded in 2024. It covers planning and project controls, procurement and tenders, compliance and securities, and BIM-to-BoQ estimation, with an AI layer called AI - IntelliSuite.
Why build a construction software website in Next.js?
The pages are long and full of motion, and they still have to load fast and read well to search engines. Next.js serves each page as ready-made HTML, React runs the interactive parts, and GSAP and Lenis handle the motion. The eleven solution pages share one template driven by data.
How do you explain eleven modules without overwhelming buyers?
Group them by job. ProcureX’s eleven solutions sit under three pillars in the menu, each with a one-line job, and every solution page follows the same order. The homepage adds two more ways in: by role and by type of project.
How do you show BIM-to-BoQ and AI features to buyers who haven’t seen the product?
Show the work happening. The BIM page separates a model into the layers of an estimate and sorts elements through its rule engine. The homepage’s AI control tower works through one billing problem, from the report to the assigned fix.
When did the ProcureX website go live?
In November 2026, at procurextech.com.
Can AI assistants read the website?
As far as any website can be. In the build we delivered, every page is HTML with its own title, description and structured data, and the coded animations keep their labels as text. The footer also links to ChatGPT, Claude, Gemini, Perplexity and Grok with a suggested prompt about ProcureX. Whether an assistant cites a page is up to the assistant.
Which tools did you use?
Figma for the design. Next.js, React, Tailwind CSS, GSAP, Lenis and Embla for the website, with Paper shaders on the AI page. Claude Code for the build, Codex for reviews and Magnific for two of the BIM visuals.
Can Rango design and build a website for our software company?
Yes. Rango designs and builds websites for B2B SaaS and AI companies in Framer, Webflow and Next.js, from a single homepage to a full website like ProcureX’s.
Explaining a complex B2B product on your website? See how we build in Next.js, how we design B2B websites, or talk to our team.
Share on
Previous
Next
