RewebTech Logo

Selected work

Platforms, products and infrastructure we've built.

Each one below covers the problem, what we shipped, and what changed afterwards — including the parts we can't name.

Sunday Hundred Group — Technology partner to a multi-brand business group

Sunday Hundred Group · Chandigarh

Technology partner to a multi-brand business group

Scope
Six-property web ecosystem · software · infrastructure and server management
Status
Live · ongoing engagement

The challenge

Sunday Hundred operates five distinct businesses under one brand — an invite-only business club, a private community for HNIs and established entrepreneurs, an investment services arm, an infrastructure and trading company, and a strategic advisory firm. Each serves a different audience at a different level of exclusivity.

One website couldn't represent all five without flattening them. Five unconnected websites would have broken the group identity that holds them together. And as the group grew, they needed a technology partner rather than a series of one-off vendors.

What we built

A parent portal at sundayhundred.com that carries the group narrative and routes each visitor to the right division, plus five independent sites on dedicated subdomains — business, onepercent, investments, infra and syndicate — each with its own positioning, content and entry path.

The parent site includes a structured FAQ layer answering what people actually search for: what the group is, how the divisions differ, which are invitation-only, and how city franchise partnerships work. Each property was built with a full search configuration — canonical URLs, social preview cards, geo-targeting and generated preview images — so every division surfaces correctly on its own.

Beyond the websites

We manage the group's servers and deployments, and handle technical operations across all six properties — hosting, domains, subdomain routing, monitoring and updates. New divisions can be brought online without a rebuild.

We're currently scoping and building the group's internal software.

Why it was built this way

Subdomains rather than subfolders, so each division can grow its own audience — and eventually its own team — without a migration. A shared design language across all six, so the group still reads as one brand to someone who only ever visits one site. Centralised infrastructure, so adding the seventh business is a configuration change and not a project.

Result

Six live properties under one identity, each independently discoverable, running on infrastructure we manage. The engagement is ongoing and now extends into their internal software.

Visit sundayhundred.com
Confidential — A multi-category local business platform with subscriptions, ads and bookings

Confidential · Chandigarh

A multi-category local business platform with subscriptions, ads and bookings

Scope
Full platform — business onboarding · subscriptions · self-serve advertising · in-app discovery · bookings
Status
Built and delivered

The challenge

Local business directories are simple to describe and difficult to build. The client wanted a platform for Chandigarh where businesses across many categories could register themselves, pay to stay listed, promote themselves without help from an admin, and take bookings directly — all without a support team doing that work manually behind the scenes.

Every one of those is a separate system, and each has to work for a shop owner with no technical background.

What we built

  • Multi-category business registration

    A self-serve onboarding flow where a business picks its category, adds its details, hours, photos and services, and goes live without an admin approving each field by hand.

  • Subscription and renewal

    Paid listings on recurring plans, with billing cycles, renewal handling, expiry and downgrade behaviour for lapsed accounts. Getting the renewal edge cases right is most of the work here: what a listing does the day a payment fails matters more than what it looks like on day one.

  • Self-serve advertising

    Businesses run and manage their own promotions inside the app, choosing placement and duration themselves, so ad revenue doesn't depend on someone selling each slot manually.

  • In-app discovery and ranking

    A search and ranking layer so businesses surface for the right categories and locations, with paid visibility boosts on top of organic placement.

  • Bookings

    Direct booking from a listing, with each business managing its own availability and requests.

Why it was built this way

Every part is self-serve by design. A directory that needs staff to onboard each business, sell each ad and confirm each booking doesn't scale past a few hundred listings. Building the operator out of the loop was the point of the architecture.

Status

Platform built and delivered to the client in full.

Gupta Associate — A working client portal for a tax and accounting practice

Gupta Associate · Yamuna Nagar, Haryana

A working client portal for a tax and accounting practice

Scope
Website · service architecture · client login and dashboard · blog · review system · compliance pages
Status
Live

The challenge

A tax and accounting practice with seven years behind it was running almost entirely on phone calls and referrals. Two problems came out of that.

Prospective clients had no way to understand what was offered before picking up the phone — so every enquiry started from zero, and anyone searching online for a specific service like GST registration or capital gains filing had no reason to find this practice over any other.

Existing clients had no way to check anything themselves. Every status update, every document request, every “has my return been filed?” arrived as a call.

What we built

  • A structured service architecture

    Each offering — income tax filing, GST and business tax, accounting and bookkeeping, year-end accounting and audits, capital gains and rental income, financial planning and reporting — lives on its own page rather than buried in a combined list. Someone searching for one specific service lands on a page that answers that specific question, and the practice can send a single relevant link instead of explaining everything on a call.

  • A client login and dashboard

    Existing clients sign in to see their own information rather than calling to ask. This is the piece that changes how the practice actually runs day to day — routine status questions stop consuming the working day.

  • A review system

    Clients leave reviews directly, so the practice builds public proof continuously instead of chasing testimonials once a year.

  • A blog

    So the practice can publish around filing deadlines and rule changes — the moments when people are actively searching — and own that traffic instead of renting it through ads.

  • Compliance pages

    Privacy policy, terms and refund policy, plus a location integration. For a practice handling other people's financial documents these aren't decoration — they're what a cautious first-time client checks before uploading anything.

Why it was built this way

Individual service pages rather than one combined page: someone searching “capital gains tax filing” and someone searching “GST registration” have nothing in common except the practice they'll end up hiring. One page can't answer both well, and it can't rank for both either.

The login was the piece that mattered most operationally. A small practice's real constraint isn't marketing, it's the founder's time — and most of that time goes on questions a client could answer themselves.

Result

Live, with each of the practice's six services addressable and shareable on its own page, and existing clients able to check on their filings through the dashboard instead of calling.

Visit guptaassociate.in

Independent work

Built outside a client engagement

Not studio deliveries — engineering built independently, included because it shows the depth behind the studio rather than what we were hired to do.

Independent work · Mobility sector, India

Real-time dispatch and driver matching, operating in India

Scope
Backend platform · rider application · driver application
Status
Live · built independently

This platform was built independently by the studio's lead developer, outside any RewebTech engagement. It sits here as evidence of the engineering depth behind the studio — not as work RewebTech was hired to deliver.

Why it's worth reading

Ride-hailing is one of the harder categories to build in. Two sides of a marketplace have to stay in sync in real time, drivers move constantly, connections drop, and every second between a ride request and a driver accepting it is a second the rider spends considering a competitor.

The operator wanted a platform of their own rather than a white-label product they couldn't control or extend.

What was built

Two applications on a shared backend — one for riders, one for drivers — with real-time location tracking, trip request and dispatch, driver matching, fare calculation, trip lifecycle management, OTP verification and payment handling. Plus an operations layer for managing drivers, trips and settlements.

The hard part

Real-time systems fail differently to normal web applications. A driver passing through a dead zone mid-trip, two riders requesting the same driver in the same second, a phone that sleeps and stops reporting location — none of these are edge cases in production, they're daily events. Most of the engineering went into making the system behave predictably when the network doesn't cooperate: state that survives a dropped connection, and a trip that recovers cleanly instead of stranding either side.

Where it stands

Live and operating in India. Client details withheld at their request.

Also built

Admin dashboards and internal tools
Subscription and billing systems
Payment and OTP integrations
Real-time location and tracking systems
Multi-brand site architectures
Server and deployment management

WORK FAQ

About the work

What is here, what is not, and why.

Can I talk to a past client?

Ask, and where the client has agreed to it we will connect you. Some projects are under NDA and cannot be discussed at all, which is why not every build appears here.

Why are some projects not listed?

Client confidentiality. Internal tools and early-stage products are often covered by an NDA, so they stay off the site even after launch.

Do you build in a specific industry?

No. The work spans commerce, fintech, health and internal tooling. What repeats is the shape of the problem — a product that has to be maintainable in year three — rather than the sector.

Have something similar in mind?

Send a short description of your project. You'll get a real reply from a developer within one business day — scope questions, an honest read on feasibility, and a ballpark number.