Dwize Care Year, Month by Month: What Happens and When

Six dates you can mark on a wall calendar

Before you sign anything, a Dwize Care Year can be reduced to six dates. Day 0 to 2 is the fit call and the contract sheet. Day 2 to 7 is onboarding. Day 7 to 45 is build and launch. Day 45 to 305 is the operating phase. Day 305 brings the renewal preview, and Day 365 is the decision: renew, or leave with your files. Everything else in the contract is either a recurring cadence (monthly, quarterly, per request) or a number attached to one of those dates.

That structure is deliberate. A year that cannot be written on a calendar is a year in which nobody can be late, so nobody is. This article walks the six dates, then gives you the same year as a month-by-month table, including the jobs that stay with you, so you can hold it against any web vendor, Dwize included.

The Dwize facts below come from the published Care Year page and the operating standards ledger, which states for each of the eight covenants what is measured, what threshold counts as met, and what Dwize does if it misses. Prices and delivery windows come from the product pages and are GST-inclusive.

Days 0 to 2: a fit call before any payment

You reach Dwize on WhatsApp, email or the contact form. Office hours are Monday to Saturday, 10:00 to 19:00 IST. The first conversation is about the job your business needs done online, not a product tour: what you sell, who has to find you, what has failed before. There are three honest outcomes. One of the four products fits. The need is too specific for any of them and is scoped as a custom Dwize Suite engagement. Or nothing fits yet, and Dwize says so.

If a product fits, a one-page contract sheet arrives within 24 hours and your delivery rhythm is assigned. Then comes the written scope, which names the package, pages, language, copy, revisions, SEO foundations, analytics, business profile and pass-throughs before you pay. Read it with a pen. It is the one document where a vague promise becomes a specific one, so ask for the export list behind the word “agreed” in the handover covenant to be written there too.

Three costs sit outside the annual price and are billed at cost: domain registration with SSL (about ₹2,100 a year) and, for App and Brand, the Apple Developer Program (about ₹9,000 a year) and a one-time Google Play Console fee (about ₹2,100). Ask for them as a line in the scope, not as a surprise in month two.

Days 2 to 7: the checklist, the kickoff call and the 30-day clock

Onboarding is a content checklist over WhatsApp or email, plus a kickoff call. Brand assets go in, and from here Dwize carries the file. The checklist is the one part of the year where you hold the pen: Dwize cannot write your doctors’ qualifications or choose your product photographs for you.

The 30-day review (covenant 07) covers this first month. If the fit is wrong in the first 30 days, the exit path is handled in writing, and the ledger describes the measure as a fit concern received and a written response with a clear next step. Use those 30 days as a test. Ask to see the line in your Care Year record that names the WhatsApp and email path (covenant 03), then send your first small request through it on a weekday afternoon and note when the reply arrives.

Days 7 to 45: build, review points and go-live

The Care Year page marks Day 7 to 45 as build and launch: build to scope, one or two milestone reviews, a go-live walkthrough, and a launch report that says what was built, what is monitored and what to do if something feels off. The delivery window differs by product.

Brand has the longest window: it is a full Store plus native iOS and Android shopping apps. The pricing page lists the same prices beside the optional add-ons, and for the exact dates on your own project you should ask for them in the written scope.

On launch day, do three things yourself before you accept the launch report. Submit the contact form and watch which inbox the message reaches. Tap every phone and WhatsApp link from a phone. Then open Search Console and Analytics and confirm that your own Google account is listed with an owner or administrator role. Dwize Site carries the analytics, Search Console and Google Business Profile foundation, and those records belong in your name. Google’s description of the owner role in Search Console is short and worth reading once.

Days 45 to 305: what “operate” contains

Updates come first because you will notice them. Twelve in-scope updates are included per year, and each is live within 2 business days of receipt. The ledger measures the gap between your message arriving and the change going live. If Dwize misses, the miss is recorded and resolved in writing. In scope means copy, images, products or content inside the product you bought. Unlimited custom development and structural rebuilds are not in scope.

The monthly check-in is the mechanism for the owner who goes quiet. At least once a month, even when you say nothing, Dwize sends a status update and one question, usually whether anything in your business has changed that should show online. The ledger counts outbound check-ins per Care Year per month, with a threshold of at least one, and a consistent miss escalates to a delivery review inside Dwize.

Maintenance happens without you. Dependency updates, OS-level patches for native apps and certificate rotation for managed domains are applied without a request, and only material changes get a mention in the check-in. For Site, delivery is static-first: pages are pre-built files, not a plugin runtime. That shrinks what has to be patched. It does not remove domain, certificate, form and listing upkeep, which is why those still appear in the calendar below.

Incidents follow a written path of five steps. Dwize detects the issue through monitoring, your report or its own review, acknowledges it through your agreed WhatsApp or email path, restores service, sends a written postmortem within 7 days of resolution (what failed, what fixed it, what changed), and records the lesson in the next check-in.

Reviews depend on the product. Store has a quarterly performance review, a half-hour call on conversion data and traffic. The Brand page lists a bi-monthly one. Every Care Year lists an annual technical review as in scope. The published pages do not say which month it falls in, so ask.

A month-by-month operating calendar you can hold any vendor to

Month 1 means the first 30 days after you sign. The middle column is what the written year says. The right column is what stays with you, about thirty minutes a month. Months 3 to 10 run the same standing rhythm, so each row picks one part of it to inspect. That is a practical way to audit a year without re-reading the contract every month.

If your current vendor cannot fill the middle column in writing, that is your answer. If you can fill the right column on your own, you hold the keys that matter, whoever your vendor is.

When a Care Year is the wrong tool

There are four situations where a Care Year is the wrong purchase, and a fit call should say so.

• You already have an engineer or a technical co-founder who maintains code you own and reviews it. A year of someone else’s calendar then duplicates what you have.
• Your site changes daily. Twelve updates are included and each further one costs ₹1,500 (GST inclusive), so if you add dozens of products a week, ask how ongoing catalogue changes are handled before you sign.
• You only need one trustworthy link for Instagram, WhatsApp and QR codes. That is what Dwize Go is for (₹2,499 a year, 7 business days), and a Site would be more than you need.
• Your current vendor answers within a day and already gives you a calendar like the one above. Keep them, and check what they send against the table.

Some things sit outside any Care Year by design: paid Google and Meta media spend, photography and copywriting (partner-fulfilled and coordinated by Dwize), App Store advertising and ASO campaigns, and any guarantee about revenue or search ranking. Inside a Care Year, Dwize does not run your ads or promise your sales.

Day 305 and Day 365: two decisions with paper in between

Sixty days before the year ends, the renewal preview arrives: next year’s price, scope and terms in writing, with a short summary of what was operated for you in Year 1. It is informational, and you do not need to act until Day 365. Use the sixty days. Put the preview beside the scope you signed and ask what changed, and why.

On Day 365, if you renew, the next Care Year starts the next day under the written terms. If you do not, covenant 08 governs the exit: agreed content and data exports, DNS guidance, deployment guidance and the other handover artifacts ship before Day 365. The ledger’s threshold is 100 percent before Day 365, and if timing changes Dwize writes a handover plan. Your domain stays yours.

For the company behind the paper, the trust page lists the registered identity and GSTIN, which you can verify yourself on the GST portal.