Work moves only when someone pushes it: copy, paste, chase, repeat. When that person is out, it stops.
What we build
Workflow software and automation that runs without the push.
WOOKhoop · Software & AI engineering
I turn chaosinto systemsthat scale.
Ashutosh Shrivastava, Founder
We design and build custom software, SaaS, apps, websites and AI systems for teams whose operations have outgrown their tools. Our focus: real estate, healthcare and financial services.
- Written scope before any invoice
- Code in your repo from day one
- NDA before you share anything
Four signs your operation has outgrown its software.
They're the four labels hanging off the tangle on our banner. Each one maps to something we build.
Every decision waits for a number someone has to assemble by hand, so meetings end with “let's check”.
What we build
One source of truth, and the reporting built on top of it.
Sales, operations and finance each keep their own version of the truth, and the versions disagree.
Escalations, workarounds and “ask the one person who knows”. The real system lives in people's memory.
What we build
Architecture with owners, monitoring and runbooks, so knowledge lives in the system.
Ten services. One engineering standard.
Every engagement starts with a written scope and ends with work you own, documented and running in your accounts.
Custom Software
For operations running on spreadsheets, inboxes and tools that don't talk to each other.
We design and build web applications, internal tools and integrations around how your team actually works. Delivered in increments you can use, on a stack your next hire can maintain.
git pushtestsstagingproduction
- ✓tests passed
- ✓migration applied on staging
- ✓preview deployed
- …production: waiting for your approval
IllustrationEvery change runs through tests and staging. Production waits for a person.
You get
- Working software in your repository, deployed to your cloud account
- Automated tests and a CI/CD pipeline from the first release
- Roles, permissions and audit logging where the workflow needs them
- Documentation and a handover session with your team
Done means
- Your team runs the workflow in the software, not around it
- Every environment can be rebuilt from the repository
- An engineer who isn't us can ship a change after handover
TypeScriptNestJSNext.jsReactPostgreSQLPrismaRedisDockerAWS
Brief a software projectThe model is not the product.
It's one component in a system that decides what the model can see, what it may do, and when a person signs off. That system is what we design, build and measure.
01 / 07
Sources & access
What it does
Defines the documents, databases and tools the system may read, scoped per user exactly as in your own apps.
Skip it and
The assistant answers from data this user was never allowed to see.
Default
Workflows first. Agents when they're earned.
If a process can be written as steps, we build it as steps and call a model only where judgement is needed. That's cheaper, faster and far easier to test. We reach for agents when the path genuinely can't be known in advance.
What we measure, on your cases
- 01Answer accuracy against a labelled set
- 02Groundedness: every claim traceable to a source
- 03Hand-off rate: how often it asks a person
- 04Latency at p95, per step
- 05Cost per request
Deepest in three industries.
We work across industries and go deepest where operations are the product. In each one, the hard part is rarely the code. It's the data rules, the handoffs and the audit trail.
What we build
- Lead intake, qualification and routing for brokers
- Property data and listing integrations
- Seller and buyer portals with document workflows
- AI that explains valuations and documents, with a human sign-off
Rules we design for
- GDPRClient and owner data in EU operations
- RESO Web APIThe US standard for exchanging listing data
- AML dutiese.g. Germany's GwG, which covers real-estate agents
- EU data residencyHosting and processing kept in-region when required
The hard part
A property valuation carries liability. We keep AI on the explaining side: it summarises comparables and drafts the report, and the number comes from a valuation provider or a person.
We design and build to these requirements. Certification, audits and legal sign-off stay with your auditors and counsel.
How an engagement runs.
Six steps, the same for a focused review or a full product build. You always know what you're paying for next.
- 01
Brief
A few minutes with the intake below. Your context arrives before the call does.
Output: a written brief
- 02
Intro call
Thirty minutes. We ask the hard questions and tell you honestly whether we're the right fit.
Output: a fit decision, both ways
- 03
Written scope
Scope, exclusions, milestones and a fixed price per phase, in writing, before any invoice.
Output: a signed scope
- 04
Architecture
Diagrams and decision records you review and approve before the build starts.
Output: approved ADRs and diagrams
- 05
Build
Working software on staging, demoed on a fixed cadence. You see progress, not status reports.
Output: accepted milestones
- 06
Handover
Code, infrastructure, docs and runbooks in your accounts. Ongoing support only if you want it.
Output: a system you run
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
Our defaults, written as decisions.
An Architecture Decision Record captures a choice, its context and its consequences. These are ours. When your requirements call for something else, we write that down too.
ADR-001Accepted
Simple architecture first
No microservices, Kubernetes, multi-agent systems, vector databases or event streaming unless a real requirement needs them.
ADR-002Accepted
The model is not the product
Design retrieval, tools, permissions, human approval, evaluation and observability before tuning prompts.
ADR-003Accepted
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.
ADR-004Accepted
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.
ADR-005Accepted
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.
Who you'll work with
Ashutosh Shrivastava
Founder, WOOKhoop · Principal Architect & AI Systems Engineer
Helping organizations turn operational complexity into sustainable growth.From his LinkedIn headline
Ashutosh is a senior software engineer and AI systems builder. He leads the architecture on WOOKhoop engagements and works alongside the engineers on the WOOKhoop team who build them.
- Company
- WOOKhoop Infotech Pvt. Ltd.
- Based in
- Bareilly, India. Remote, across time zones
- Focus
- Real estate · Healthcare · Financial services
Start a project brief.
A few questions, one at a time, about three minutes. Pick an option or just type. You'll see the brief build as you go, and nothing is sent until you choose to send it.
WOOKhoop intakeAutomated · not a live person
Talk to a person ↗Hi. I'm WOOKhoop's intake assistant. I'm automated, not a person.
I'll ask about ten short questions so your call can start with specifics. Nothing is sent until you review your brief and choose to send it.
Straight answers.
If yours isn't here, ask it on the call.
Get new writing from Ashutosh in your LinkedIn feed.
The WOOKhoop newsletter is published on LinkedIn. Subscribing takes one click, and you can leave just as easily.