How we work
How we work: process, pricing and terms
What happens after the first call: four steps and what you get at each, how pricing and payment work, and who holds the keys.
Talk to an engineer, not a salesperson.
Process
Bring us the problem, not the spec.
Four steps. Every step ends with something you can read and keep.
Discover
We learn the problem, the people it's for, the constraints and what already exists.
You get
A written brief
Architect
We design the system and write down the key decisions before anyone builds.
You get
An architecture doc, the key decisions (ADRs) and a milestone plan with estimates
Build
We build in small, reviewable steps against the agreed architecture.
You get
Regular demos and written updates
Validate and hand over
We test the failure paths as well as the happy one, then hand over.
You get
UAT sign-off and handover notes
Illustrative sample, not from a client project
ADRADR-004 · Verify payments against the chain before releasing a reportIllustrative sample, not from a client project
Illustrative sample, not from a client project. The project, dates and figures are invented to show the format.
ADR-004 · Verify payments against the chain before releasing a report
In plain English
Before we hand over a paid report, we check the payment on the blockchain ourselves. We don't rely only on the payment service telling us it arrived.
Context
The API charges an AI agent per report. A payment service confirms payments by calling our server. Those calls can be delayed, repeated or, in the worst case, forged. A report released on a false confirmation is a report given away.
Decision
A confirmation only starts the process. Before releasing a report, the server reads the transaction from the chain, checks the amount, the recipient and that it succeeded, and records the payment once. A second confirmation for the same payment is ignored.
Alternatives considered
- Trust the payment service's confirmation. Simpler and faster, but one forged or replayed call releases a report for free.
- Wait for a longer confirmation depth on every payment. Safer, but slower for every user, even for small amounts.
Consequences
- Each paid request makes one extra read from the chain. Budgeted in the milestone plan.
- Payments can't be counted twice, and there's a test for that case.
- If the chain node is unreachable, reports wait rather than release. The app shows "payment confirming", not an error.
Revisit when
Payment volume makes the extra read a real cost, or the payment service offers signed, verifiable confirmations.
Illustrative sample, not from a client project. The project, dates and figures are invented to show the format.
UAT checklistUser acceptance · Milestone 2 · Example project: paid-report APIIllustrative sample, not from a client project
Illustrative sample, not from a client project. The project and dates are invented to show the format.
User acceptance · Milestone 2 · Example project: paid-report API
You test on the staging app with your own account. Tick each line when it works the way we agreed. Anything that doesn't goes into "Not accepted", and we fix it before sign-off.
| # | Check | Accepted |
|---|---|---|
| 1 | An agent without payment gets "payment required", with the price | ☐ |
| 2 | An agent that pays gets the report | ☐ |
| 3 | Paying twice by mistake charges once | ☐ |
| 4 | The report shows the transaction it was paid by | ☐ |
| 5 | A report that fails after payment is refunded | ☐ |
| 6 | An agent that reaches its spending limit is stopped, with a clear message | ☐ |
| 7 | The admin view lists payments, refunds and limits | ☐ |
Not accepted (with a reason)
- {item, reason, agreed fix, date}
Sign-off
- Accepted by: {client's product owner, role}
- Date: {date}
Illustrative sample, not from a client project. The project and dates are invented to show the format.
What we don't promise: guaranteed timelines, returns, or bug-free code. Estimates come with their assumptions written down.
Pricing
How pricing works
The shape depends on how clear the scope is. We scope against your budget range rather than quoting before we understand the problem.
Discovery sprint
- When it fits
- The scope isn't clear yet, you need a proof of concept, or a running system needs a review first.
- What you get
- An architecture doc, a risk list and a milestone plan with estimates.
Fixed-price milestones
- When it fits
- The scope is clear: an MVP, a dApp, an integration.
- What you get
- A fixed price for each milestone.
Dedicated engineer, monthly
- When it fits
- Ongoing product work after launch, or a long build.
- What you get
- An engineer on your product by the month, in your tools and repo.
Hourly
- When it fits
- Small tasks, and focused work inside a system that's already running.
- What you get
- Time logged against an agreed task list.
What changes the price
- How many systems, chains and integrations are involved.
- Whether the product holds or moves money.
- How much existing code there is to learn first.
- Your timeline, and the testing the risk calls for.
“Anupam did an excellent job! Everything was completed exactly as agreed in the contract, with great attention to detail and professionalism. I truly appreciate the hard work and commitment…”
Reviews are verbatim from client contracts delivered through Upwork. '…' marks where a quote was shortened. Client names stay private.
Payment
How you pay
- Bank transfer (USD)
- An international transfer, invoiced in US dollars.
- Escrow (optional)
- If you'd rather pay into escrow, we also contract through Upwork, which holds each milestone's funds until you approve the work.
Hours
Hours and time zones
We work in English, Hindi and Bengali.
For US teams the overlap is short, so we agree call times up front and keep everything else in writing.
Security
Security and key custody
- For anything holding real value, we recommend an independent audit before mainnet, and we prepare the code and documents for it. Our review is engineering diligence, not a substitute for a formal audit.
- Please don't send private keys, seed phrases or passwords by chat, email or WhatsApp.
For larger organisations
Working with larger organisations
- Certifications
- We don't hold SOC 2 or ISO 27001.
- A first step
- A fixed-fee discovery sprint or proof of concept, with a written report.
FAQ
Questions people ask before they hire us
Are you a team or a freelancer?
A founder-led team. Anupam founded Techmax Labs and leads the engineering. The client reviews on this site are from projects Anupam delivered.
About page Client reviewsWho will I actually talk to?
An engineer, not a salesperson.
Do I need a full spec before we talk?
No. Bring the problem: what it's for, who uses it and what exists today. Discovery turns that into a written brief, then an architecture and a milestone plan with estimates. If you already have a spec, we work from it and tell you where we'd question it.
DiscoveryWhat happens after I send a brief?
An engineer reads it and replies with questions, not a sales deck. If it looks like a fit, we suggest a 30-min call. If it doesn't, we say so, and we'll tell you if the answer is simpler than hiring us.
How does pricing work?
It depends on how clear the scope is. When it isn't clear yet, we start with a short paid discovery. When it is, you get a fixed price per milestone. For ongoing work, a monthly engineer. We scope against your budget range rather than quoting before we understand the problem.
See pricingCan I pay into escrow instead?
Yes. Escrow is one of our payment options: a third-party platform holds each milestone's funds until you approve the work. The process stays the same.
How you payWant to talk it through?
Book a 30-min call, or send a brief if you'd rather write first.
Or message us:WhatsApp, opens in a new tab
WhatsApp: +91 90644 79521, opens in a new tab