Node · v19

Each service has an per-hour band.

Projects bill by the hour. Months use that hour times thirty. Pick a line to pay while signed in, or talk scope on the reach engineers intake brief.

Published per-hour band ₹100 – ₹5,000 / hr

Hourly rates. A month is the hourly rate times 30.

Published rate × multiplier = figure on this page

Try the published arithmetic

Choose a line from the catalog. Monthly lines multiply the hourly rate by thirty. Project lines multiply by hours you enter — the hourly rate still comes from the sheet.

Published line Hours in scope (project lines only)

Without JavaScript — worked example from this page

Website care at ₹300 / hour × 30 = ₹9,000 / month

Project lines show the hourly starting rate until a written scope names hours. Sending the contact form does not create an invoice.

Every published line

One register — not a row of matching cards. Open the service lane for scope; pay or email from the row.

Websites

Landing pages and company sites for businesses that need a clear public presence, not a theme with a logo dropped on it.

Line	Shape	Published figure	Actions
Landing page One page: the offer, the proof, and a way to enquire.	Project (hourly)	₹500 / hour	Run billing handoff for this line Discuss scope by email first
Business website A multi-page company site with a clear path from arrival to enquiry.	Project (hourly)	₹2,500 / hour	Run billing handoff for this line Discuss scope by email first
Website care A monthly block for edits, small fixes, and someone who already knows the site.	Month (×30)	₹9,000 / month₹300 / hour × 30	Run billing handoff for this line Discuss scope by email first

Custom software

Internal tools and a first product release, with discovery priced before product code starts.

Line	Shape	Published figure	Actions
Discovery Scope, risks, and a build plan you can approve before product code.	Project (hourly)	₹1,000 / hour	Run billing handoff for this line Discuss scope by email first
Business application An internal tool for a workflow your team currently runs in inboxes and sheets.	Project (hourly)	₹4,000 / hour	Run billing handoff for this line Discuss scope by email first
SaaS MVP The first sellable release of a product: accounts, the core job, and a way to pay attention to usage.	Project (hourly)	₹5,000 / hour	Run billing handoff for this line Discuss scope by email first

AI software

Pilots, application sprints, and agent workflows with a person still responsible for what gets sent.

Line	Shape	Published figure	Actions
AI pilot A bounded first version of one AI-assisted job, with review before anything is sent.	Project (hourly)	₹1,500 / hour	Run billing handoff for this line Discuss scope by email first
AI app sprint A short build of an AI feature inside a product or internal tool.	Project (hourly)	₹2,500 / hour	Run billing handoff for this line Discuss scope by email first
AI agents Agents for a defined queue — intake, triage, or document handling — with a person in the loop.	Project (hourly)	₹5,000 / hour	Run billing handoff for this line Discuss scope by email first

Automation

The repetitive handoff between inbox, sheet, and system, built once and left running.

Line	Shape	Published figure	Actions
Single workflow One trigger, one destination, and a person for the exceptions.	Project (hourly)	₹500 / hour	Run billing handoff for this line Discuss scope by email first
Multi-step workflow Several systems, written decisions, and a path when a step fails.	Project (hourly)	₹1,500 / hour	Run billing handoff for this line Discuss scope by email first
Document processing Packets in, structured fields out, with a review queue for low-confidence reads.	Project (hourly)	₹2,500 / hour	Run billing handoff for this line Discuss scope by email first

Capacity

Prepaid hours and monthly blocks for work that is real, but does not fit a single fixed scope.

Line	Shape	Published figure	Actions
Monthly care A monthly block for a moving queue of engineering or site work.	Month (×30)	₹15,000 / month₹500 / hour × 30	Run billing handoff for this line Discuss scope by email first
Monthly plus A larger monthly block when one stream of work needs regular attention.	Month (×30)	₹30,000 / month₹1,000 / hour × 30	Run billing handoff for this line Discuss scope by email first
Engineering month A reserved monthly block for a dedicated stream of work.	Month (×30)	₹60,000 / month₹2,000 / hour × 30	Run billing handoff for this line Discuss scope by email first

Search and content

On-page search, a content model, and a monthly writing block for pages that should be found.

Line	Shape	Published figure	Actions
Search audit A written review of the public site and the pages that are missing.	Project (hourly)	₹800 / hour	Run billing handoff for this line Discuss scope by email first
Search programme The audit, then the pages, titles, and internal links to match it.	Project (hourly)	₹2,000 / hour	Run billing handoff for this line Discuss scope by email first
Content month A monthly writing block for new pages and revisions.	Month (×30)	₹15,000 / month₹500 / hour × 30	Run billing handoff for this line Discuss scope by email first

Integrations

Connect the tools you already pay for, with a map of what talks to what and who owns the failure.

Line	Shape	Published figure	Actions
Single connection One pair of tools, one direction, exceptions to a person.	Project (hourly)	₹1,000 / hour	Run billing handoff for this line Discuss scope by email first
System map Several tools, a written source of truth, and the connections that follow.	Project (hourly)	₹2,500 / hour	Run billing handoff for this line Discuss scope by email first
Integration care Monthly hours for breaks, field changes, and new endpoints.	Month (×30)	₹9,000 / month₹300 / hour × 30	Run billing handoff for this line Discuss scope by email first

Support

A named contact and a monthly hour block for the small breaks that should not become a project.

Line	Shape	Published figure	Actions
Support starter A small monthly block for fixes across work we already know.	Month (×30)	₹6,000 / month₹200 / hour × 30	Run billing handoff for this line Discuss scope by email first
Support plus A monthly block when several systems need a regular eye.	Month (×30)	₹12,000 / month₹400 / hour × 30	Run billing handoff for this line Discuss scope by email first
Launch watch A short, heavier block for the two weeks after something goes live.	Project (hourly)	₹600 / hour	Run billing handoff for this line Discuss scope by email first

Included on this sheet

The hourly starting rate for each named line, ending in zero, inside the published band.
For monthly lines, both the hour and the hour × 30 figure, so the multiplication is visible.
A written scope after contact — the figure that applies is confirmed there, not implied by the form.
Checkout for a chosen line while signed in, then the secure gateway handoff described on the pay pages.

Not included

Sector multipliers, unlisted discounts, or a ranking promise tied to the rate.
Rolled-over hours from a previous month — the allocation refreshes; unused time does not become a balance.
Silent bundling of project and care — they can sit side by side, but they stay separate engagements.
An invoice or reserved rate from sending the contact form alone.

How to pay

Pick a line on this register (or on the matching service lane).
Run billing handoff for this line — opens checkout while you are signed in; billing details go to the gateway with that package line.
Processor ack — the return page shows whether the gateway captured the checkout.

Billing details are sent to the secure processor with this handoff — not stored in the page.

How to start without paying yet

Discuss scope by email first — the form can open with the service and package already selected. A confirmation is emailed to the address you enter; work starts when the scope is confirmed.

Send a note to engineers

How to read a rate

The number is an hourly starting rate. A month multiplies it by thirty.

Each line on this page is a kind of work with an hourly rate between the studio minimum and maximum, and the amount ends in zero. A landing page at 500 is ₹500 an hour. Website care at 300 is ₹300 an hour, which is ₹9,000 for a month because the month is thirty times the hour.

The same rule covers support, content, capacity, and integration care. We show both figures so a monthly line cannot be mistaken for a one-day project, and a project line cannot be mistaken for a retainer.

These rates are starting points for that shape of work. A written scope can confirm the figure or explain why the job is a different shape. Sending a form does not reserve the rate and does not create an invoice. Work starts when the scope is confirmed.

Project or month

Use the cadence that matches the queue.

Project

The job ends. The block ends.

A page, a discovery, a workflow, a pilot, a connection, a launch watch.
Priced per hour for that shape.
A surprise becomes a new block instead of a silent overrun.

Month

The queue does not end. The allocation refreshes.

Care, support, content, capacity, integration care.
Displayed as the hourly rate times 30.
Unused hours in the month do not roll forward.

Neither yet

Leave word for the desk without picking a line.

The form allows “not sure yet”.
We will recommend a service if the note is specific.
If it is not specific, the reply will ask for the missing edge.

Reading the engagements page

Why does a monthly line show two amounts?

The large figure is the hour times 30. The small figure is the hourly rate, so you can see the multiplication instead of trusting a bundled month.

Can two lines be combined?

They can sit next to each other as separate engagements. A business website and website care are not one silent package. You can buy the site and decline the care.

Is the rate on the page the invoice?

No. It is the starting rate for that kind of work. The scope we email after you contact us is the figure that applies.

What if my job is larger than the line?

Say so in the message. A SaaS MVP and an engineering month are different shapes. We would rather re-scope than pretend a small line covers a platform.