About WOOKhoop

WOOKhoop (WOOKhoop Infotech Pvt. Ltd.) is a software and AI engineering company based in Bareilly, India. It designs and builds custom software, SaaS products, apps, websites, AI systems and automations for teams whose operations have outgrown their tools, with a focus on real estate, healthcare and financial services. It was founded by Ashutosh Shrivastava, who leads the architecture on every engagement.

We also run WOOKhoop Commercials, our AI production studio for films, motion graphics and campaign imagery. Two practices, one company, led by the same founder.

One company · two practices

Systems that work. Stories that move.

WOOKhoop builds software and AI systems. WOOKhoop Commercials brings brands to life through film, motion and imagery. Same company, same founder, the same care from brief to delivery.

Founder · both practices

Ashutosh Shrivastava

Founder, Principal Architect & AI Systems Engineer

WOOKhoop

Parent

Custom software, SaaS and AI systems.

Software and AI engineering for teams in real estate, healthcare and financial services whose operations have outgrown their tools.

Legal entity
WOOKhoop Infotech Pvt. Ltd.
Based in
Bareilly, India
Explore our engineering services

The studio portfolio shows labelled concept projects with fictional brands, unless stated otherwise.

Key facts

Writing about us? These are the facts to use.

Legal name
WOOKhoop Infotech Pvt. Ltd.
Based in
Bareilly, India. Works remotely with clients in the United States and the European Union, across time zones.
Focus industries
Real estate, Healthcare, Financial services. Other industries when the problem fits.
Typical stack
TypeScript, NestJS, Next.js, React, PostgreSQL, Prisma, Redis, Docker, AWS (ECS), Python, FastAPI, LLM APIs, Vector search
How we're engaged
Written scope with exclusions, milestones and a fixed price per phase. Payment follows accepted milestones.
Ashutosh Shrivastava, founder of WOOKhoop.

Founder

Ashutosh Shrivastava

Founder, WOOKhoop · Principal Architect & AI Systems Engineer

Ashutosh is a senior software engineer and AI systems builder with a bachelor's degree in computer science. He has been building software since 2018: first as a freelancer delivering small custom projects, then as the founder of WOOKhoop, where he leads the architecture on every engagement and works alongside the engineers who build them.

He also leads creative direction at WOOKhoop Commercials, working with the team that produces, edits and finishes the studio’s films and imagery.

Helping organizations turn operational complexity into sustainable growth.From his LinkedIn headline

LinkedIn profile · Newsletter on LinkedIn

How we work, written as decisions

An Architecture Decision Record captures a choice, its context and its consequences. These are our defaults. When your requirements call for something else, we write that down too.

  1. ADR-001 · Accepted

    Simple architecture first

    No microservices, Kubernetes, multi-agent systems, vector databases or event streaming unless a real requirement needs them.

    Context
    Complexity is the most expensive thing you can add to a system, and the hardest to remove.
    Consequences
    Faster delivery, lower cloud bills, and fewer people needed to run it.
  2. ADR-002 · Accepted

    The model is not the product

    Design retrieval, tools, permissions, human approval, evaluation and observability before tuning prompts.

    Context
    In our experience, AI features fail on missing context, permissions and evaluation far more often than on the choice of model.
    Consequences
    Changing models becomes a configuration change, not a rewrite.
  3. ADR-003 · Accepted

    Workflows before agents

    Build deterministic workflows and call a model only where judgement is needed. Use agents only when the path can't be known in advance.

    Context
    Most business processes can be written down as steps, and steps can be tested.
    Consequences
    Cheaper to run, faster to respond, and explainable when something goes wrong.
  4. ADR-004 · Accepted

    MVP, production and scale are different systems

    Every proposal says which of the three you're buying, and what has to change to reach the next.

    Context
    Building for a million users on day one spends the budget that should find the first hundred.
    Consequences
    No surprise rewrites, and no infrastructure you pay for before you need it.
  5. ADR-005 · Accepted

    Claims match the architecture

    We only call something secure, scalable or production-ready when the design, the tests and the operations support it, and we show you the evidence.

    Context
    Those words are easy to say and expensive to be wrong about.
    Consequences
    You can hold us to every sentence on this page.

In writing, before you pay

These go into the contract, not just onto this page.

  • Code in your repository from the first commit
  • IP assigned to you in the contract
  • NDA before you share anything confidential
  • Fixed scope and written exclusions per phase
  • Payment tied to accepted milestones
  • No subcontracting without your written approval

The coil

Our mark is one line pulled out of a tangle and wound into a coil. It's the job in one picture: take operational chaos and turn it into a system that holds.

Want to see if we're the right fit?

Start a brief or book thirty minutes. We'll tell you honestly, either way.