Website launch and care

Proposed implementationLink

Use maintainable WordPress as the working default, native editor and reusable sections where practical. Choose a familiar builder only when it materially helps without weakening maintenance, performance or accessibility. Select hosting, forms, mail, backups and analytics against actual needs. Nusigma owns accounts and renewal responsibility.

Use calm typography, clear hierarchy and useful genuine imagery. Both audiences need complete mobile journeys. Avoid fictitious team imagery and unnecessary subscriptions.

Proposed release budgetLink

Cap initial founder effort at 40 hours: scope/assets 4, content 10, design/build 16, verification 6 and contingency 4. This is a hypothesis, not a guaranteed estimate. Schedule it within non-client time or explicitly replace other work; it does not sit on top of a full client calendar.

Release checksLink

• Content: verify company particulars, founder role, capability claims, permissions and any published prices; remove placeholders.

• Experience: check both audience journeys on phone and desktop, keyboard, zoom, focus, contrast, headings, images and form errors.

• Enquiries: submit externally; verify acceptance, storage, notification, reply routing, spam controls and deliberate failure handling.

• Operations: confirm authorized access, supported dependencies, backup and restore process, rollback, account ownership and renewals.

• Discovery: check titles, descriptions, links, sitemap, indexing, canonical destinations, useful missing-page behavior and known old-URL mappings.

• Privacy and measurement: match explanations to actual tools; keep enquiry content out of analytics.

Protect identity and releaseLink

Inventory domain and mail settings before DNS or hosting changes. Preserve records supporting vimal@nusigma.in and test external sending and receiving afterward. Vimal approves the final preview and release timing. Check the real public form, routes, secure transport and indexing immediately after release, then after day one and week one.

Ongoing ownership and measurementLink

Vimal owns content, updates, renewals, enquiry checks and recovery readiness. Maintain the dependency inventory and check backups and compatibility before updates. Recovery planning includes site files and database.

Measure audience-route clicks, contact clicks, accepted submissions, qualified enquiries and paid progression separately. Review around day 30 for failures and day 90 for patterns, with enough volume to interpret them. A click is not an enquiry and traffic is not commercial success.