How We Deliver
Our delivery is structured to give you maximum visibility, predictable outcomes, and a team that takes ownership end-to-end.
Your Delivery Team
Project Manager
Your single point of contact. Responsible for timelines, communication, risk management, and keeping the project on track. You can reach them anytime during working hours.
Functional Consultant / Business Analyst
Leads requirement gathering, ERPNext configuration, and process mapping. Works directly with your department heads to ensure the system matches your real workflows — not a textbook template.
Developer(s)
Handle all custom development — custom DocTypes, scripts, reports, integrations, and workflows. Work from clearly defined tickets to produce reliable, tested output.
QA Engineer
Tests every configured module and developed feature before it reaches you for User Acceptance Testing. Catches issues early so your UAT is clean.
Account Manager
Stays across the project independently of the delivery team. Touches base with you regularly to ensure expectations are being met and escalates proactively if anything is off track.
Development Methodology
We use Scrum for ERPNext implementations — structured 2-week sprints, each delivering a testable set of configured modules or custom features.
A typical sprint cycle:
- Sprint Planning — define what gets built/configured this sprint
- Development & Configuration — team works through tickets
- Internal QA — QA engineer verifies output
- Demo — we show you what was built; you provide feedback
- UAT — you test in the staging environment
- Sprint Retrospective — what worked, what to improve
For smaller projects or ongoing support, we use Kanban — a continuous flow model with no fixed sprint boundaries.
Meeting Cadence
| Meeting | Frequency | Purpose |
|---|---|---|
| Daily Standup | Daily (async via Slack) | Progress, blockers |
| Client Sync | Weekly | Status update, demo, Q&A |
| Sprint Planning | Every 2 weeks | Define upcoming sprint scope |
| UAT Review | Per sprint | Client testing and sign-off |
| Steering Review | Monthly | Overall progress, risks, decisions |
Reporting
You will receive a weekly status report covering:
- What was completed this week
- What is in progress
- What is coming next
- Any blockers or risks
- Open action items (yours and ours)
For time & material engagements, you'll also receive a monthly hours report detailing exactly where time was spent.
Escalation Matrix
| Level | Contact | When to Use |
|---|---|---|
| 0 | Project Manager | Day-to-day issues, delays, quality concerns |
| 1 | Delivery Head | If PM is unresponsive or issue remains unresolved |
| 2 | Account Manager | Client relationship, commercial concerns |
| 3 | Founder (Chinmay Kulkarni) | Critical escalations requiring executive attention |
We never leave an escalation unacknowledged. All escalations get a response within 4 business hours.
Scope Changes
Scope changes happen — requirements evolve. When they do, we:
- Document the change clearly
- Estimate additional effort and timeline impact
- Get written approval before proceeding
- Update the project plan accordingly
No surprises on invoices. Ever.
Testing & UAT
Before any module is handed to you for UAT:
- Functional Consultant verifies configuration against BRD
- QA Engineer runs structured test cases
- All bugs found internally are fixed before handover
Your UAT is for business validation — not bug hunting. We handle the bug hunting.
