The Consulting building in the 8xWork world

06The Consulting building

Make the next technical decision with clarity.

We assess feasibility, review existing systems and define the architecture, budget and delivery plan. Use the findings to commission a new build or decide how to improve a stalled project.

Start a project How we work

Discovery · Architecture · Delivery · Projects from ₹5 lakh

Floor 01 · How we work

Four stages. Something concrete to review at each.

We agree responsibilities, review points and acceptance criteria before the build. Each stage produces something concrete to discuss.

01
Define the brief.
Map the users, current process and intended result. Prioritise the first release and identify dependencies, budget and decision-makers.
You review: the scope & acceptance criteria.
02
Review the approach.
Review the important decisions through a prototype, storyboard or technical plan. Resolve the largest unknowns before full production.
You review: a prototype, plan or sample.
03
Build and test.
See working releases at agreed milestones. Check complete journeys and record feedback against the approved requirements.
You review: working milestones & test results.
04
Launch and hand over.
Complete acceptance checks and the agreed documentation, access and training. Confirm who owns operation, maintenance and the next release.
You review: the release & handover pack.

Floor 02 · What you get

What your engagement can include.

The proposal defines the deliverables selected for your project, their depth and how they will be reviewed.

Process & requirements

Map stakeholders, existing workflows, constraints and the intended result.

Feasibility & architecture

Assess options, integration needs, risks and technical trade-offs.

Scope & commercial plan

Priorities, work packages, assumptions, milestones and a basis for a project quote.

Delivery coordination

Review cadence, responsibilities, acceptance checks and handover planning where included.

Typical projects

An ambitious idea with an unclear technical route
A software and hardware project with multiple dependencies
A stalled project that needs an independent assessment
A team that needs a scope, roadmap or delivery partner

Floor 03 · An example we can scope

An existing build that needs a credible next step

An example brief: a team has a partial product and needs to decide whether to repair, extend or rebuild it. The assessment starts with authorised access and the intended business journeys.

01
Review requirements and the current build
02
Map gaps, dependencies and technical risks
03
Compare practical options and trade-offs
04
Define a prioritised release and delivery responsibilities

Illustrative project brief

Floor 04 · Scope & cost

Which decision is holding your project back?

We scope consulting within a defined project engagement, with clear outputs and decisions. The minimum engagement is ₹5 lakh. An introductory call helps establish whether the project and our team are a fit before a paid scope is proposed.

International proposals are available in USD. Your proposal identifies dependencies, review milestones and acceptance criteria, with recurring licences, hardware, travel and support itemised where relevant.

The decision to make

State what the engagement must help you decide, who owns that decision and which constraints matter most.

Available evidence

Confirm access to requirements, repositories, architecture, vendor documentation and relevant stakeholders.

Depth & outputs

Agree the review boundaries, demonstrations or prototypes needed, and the format of findings and recommendations.

Discuss your requirements

Floor 05 · Review & handover

Make completion something you can check.

We use the agreed scope to define the reviews and evidence your team needs before acceptance.

Tie recommendations to the reviewed requirements and evidence.
Make assumptions, dependencies and unresolved questions explicit.
Compare the viable options and their consequences.
Review a prioritised plan with responsibilities and acceptance criteria.

The handover belongs in the plan.

Receive the agreed assessment, architecture or process maps, decision record and proposed work packages. Implementation, project coordination and subsequent reviews are scoped explicitly.

Floor 06 · Projects

Projects to explore.

Healthcare · Immersive learning

NursingVR

Interactive VR for nursing education, with clinical content co-designed with AIIMS faculty.

View project

Healthcare · Software platform

Sound for Silence

Android and web tools for an AIIMS auditory verbal therapy initiative, connecting families, therapists and hospital teams.

View project

Floor 07 · Questions

Project questions.

Can we start with consulting before development?

Yes. A defined discovery and architecture engagement can come before a build. Its outputs and commercial scope are agreed separately.

Will you review an existing vendor's work?

We can review authorised project materials against agreed requirements and report technical findings. Any implementation or migration is a separate scope.

Can you manage a project involving hardware and software?

Yes. We map the interfaces, dependencies and responsibilities across the workstreams, then agree how progress and acceptance will be reviewed.

What happens after the first call?

If there is a fit, we request relevant project information and prepare the next proposed engagement. A call is not a commitment to a budget or delivery date.

Next building

Let’s scope your next step.

Bring the problem, the intended users and your priorities. We’ll discuss the scope, budget and next step. A finished specification is optional.

Start a project Projects from ₹5 lakh

Make the next technical decision with clarity.

Four stages. Something concrete to review at each.

Define the brief.

Review the approach.

Build and test.

Launch and hand over.