Vedatricks
Book a 30-minute call

Engagements

You can open the work in progress whenever you like.

Four phases, each ending in something you can open, read or keep: a written scope, a staging URL, a handover, a support route.

The engagement

From first call to running system.

  1. Scope

    You get: a written scope

    One call to understand the problem, then a written scope: what is included, what is explicitly not, the price and the sequence.

  2. Build

    You get: a staging URL

    Work happens on a staging environment you can open at any time. Changes ship in small pieces so feedback is cheap.

  3. Launch

    You get: production and handover

    DNS, TLS, analytics and backups are set up before go-live, and you receive the handover notes and every credential.

  4. Run

    You get: monitoring and a support route

    Uptime monitoring, alerts and a named route for changes. Support terms are agreed in writing before launch.

Standards

What ships with every build.

These are not upsells. They are the baseline we hold our own products to, so client work gets them too.

  • HTTPS everywhere, behind Cloudflare

    TLS, security headers and a WAF in front of the site, with challenge and rate limiting on the endpoints that accept input.

  • Accessibility to WCAG 2.1 AA

    The target for everything we build, in line with IS 17802. Keyboard paths, contrast and focus states are part of review, not a retrofit.

  • A performance budget, measured on real users

    LCP under 2.5 s, INP under 200 ms and CLS under 0.1 on a 4G phone — measured in field data, not a lab score.

  • Analytics from day one

    First-party, cookieless-by-default analytics installed at launch so you can see traffic and conversions without a third-party tag.

  • Backups before every migration

    Production databases are dumped before a schema change, and a production deploy is reviewed before it goes out.

  • Source you own, in version control

    Every project lives in a repository with CI, a secret scan and a documented deploy — handed over at the end of the engagement.

Principles

How the team decides.

  • You ship to production

    Three products are live on their own domains. Work goes out behind CI, a reviewed deploy and a database backup taken before every migration.

  • Claims match the code

    We publish only what is shipped. A feature that is in build is labelled “in build” — on this website, in the product and in the sales conversation.

  • Customer data is not a shortcut

    Tenant-scoped by default, fail-closed. Encryption, consent records and audit logs are part of the feature, not a later ticket.

  • We run on our own software

    Our ERP, CRM, mail, monitoring and analytics are built in-house. You will use what the company builds, every day, and file the first bug.

Working together

Agreed in writing before anyone starts.

The terms below are agreed in writing at the start of a project, not improvised halfway through.

Start a project
Office hours
Mon–Sat, 10:00–19:00 IST
Where the work is
A staging URL you can open at any time, and a repository with CI, a secret scan and a documented deploy.
Change requests
Anything outside the written scope is quoted before it is built. No silent scope creep, no surprise invoice.
At handover
DNS, TLS, analytics and backups configured before go-live, then the handover notes and every credential.
After launch
Uptime monitoring, alerts and a named route for changes. Support terms are agreed in writing before launch, not after.

Tell us what needs building.

A call with someone who will work on it, then a written scope.

Talk to an engineer Read the security posture
Not ready for a call?

Cookie settings

Choose what you allow. You can change this at any time from “Cookie settings” in the footer, and withdrawing is as easy as allowing.

  • Remembers choices you make on the site, such as your preferred language for the website assistant.

  • Vedatricks Analytics is first party and cookieless by default: it counts page views without writing an identifier to your device. A cookie is only set if you opt in, and only to avoid counting the same visit twice.

  • Strictly necessary Always on

    Needed for the site to work: to remember your consent choice, to protect forms from automated abuse and to keep you signed in to a Vedatricks product. These are not used for advertising and cannot be switched off from the banner.

  • Payments Always on, but only on checkout pages

    Razorpay Checkout sets its own cookies when it loads, which happens only on pages where you are actually paying. Razorpay is the controller of those cookies; see Razorpay’s privacy policy.

Full detail of every cookie is in the Cookie Policy register.