Skip to content
sedwis

Consult & Support

Support that answers before you chase.

Monitoring, patching, upgrades and fixes with response times written into the contract.

Sound familiar?

  • The developer who built your system stopped replying months ago.
  • You find out the site is down when a customer calls.
  • Your dependencies haven't been updated in two years and you know that's a problem.

If any of those land, this is the page for you. Here's how we approach it.

What you get

What maintenance & support actually changes.

01

Guaranteed response times

Written SLAs by severity, so a production outage doesn't depend on someone's goodwill.

02

Problems found first

Uptime, error and performance monitoring that alerts us before your customers notice.

03

Security kept current

Dependency and patch management on a schedule, not when something breaks.

04

Backups that restore

Automated backups with restores actually tested — an untested backup isn't a backup.

05

Continuity of knowledge

A team that knows your system, so a resignation doesn't erase the context.

06

Predictable cost

A fixed monthly figure instead of emergency rates when something fails.

What's included

Everything in the engagement.

Uptime monitoring

Continuous checks with alerting to a human.

Error tracking

Exceptions captured, triaged and fixed.

Security patching

Dependency and OS updates on schedule.

Backups

Automated, offsite and restore-tested.

Performance monitoring

Core Web Vitals and server metrics tracked over time.

Bug fixes

Resolution within agreed severity SLAs.

Small enhancements

Agreed monthly hours for changes.

Monthly reporting

Uptime, incidents, work done and what's coming.

How we deliver

You'll know where it stands every week.

01

Discovery

1–2 weeksScope document, risk list and a fixed estimate
02

Design & architecture

2–3 weeksClickable prototype and system design
03

Build

6–16 weeksA working demo at the end of every sprint
04

Test & harden

ContinuousAutomated test suite, UAT sign-off, security review
05

Launch

1 weekProduction deployment, monitoring and full handover
06

Support

90 days includedSLA-backed fixes and a roadmap for what's next

Engagement models

Pick the risk model that suits you.

Indicative starting points. We give a firm number after discovery — a fixed price quoted before we understand the scope is a number designed to be revised.

Fixed scope

₹8,00,000

starting from

A clear brief you want delivered to a firm budget

  • Fixed price agreed after discovery
  • Defined deliverables and milestones
  • Change requests quoted separately
  • 90 days post-launch support

Dedicated team

₹3,50,000 / month

starting from

Evolving requirements, or an in-house team that needs capacity

  • Senior engineers embedded in your standups
  • Scale the team up or down monthly
  • You set the priorities each sprint
  • Direct access — no account manager layer

Retainer

₹1,20,000 / month

starting from

Ongoing improvement, maintenance and support after launch

  • Agreed monthly hours
  • Guaranteed response times
  • Monitoring, patching and dependency upgrades
  • Quarterly roadmap review

FAQ

Maintenance & Support questions.

Still have one? Talk to an engineer, not a salesperson.

Yes, and about half our support clients are in that position. We start with a paid onboarding audit to understand the system and document it — going in blind would mean guessing during an incident.

Typically one business hour for a production outage, four for a major issue and one business day for minor items. Exact figures go in the contract, and we report against them monthly.

Monitoring, patching, backups, bug fixes and an agreed block of hours for small changes. Larger feature work is quoted separately so the retainer stays predictable.

For systems that need it, yes, at a higher tier. Most businesses do fine with extended business hours plus out-of-hours cover for genuine outages — and we'll advise honestly on which you need.

Start the conversation

Tell us what you need.

An engineer replies within 4 business hours — with questions, not a brochure.

NDA available before you share anything.

A range is fine. It helps us scope honestly.

What are you building, what's the problem, and what does success look like?

An engineer replies within 4 business hours.