Aparna Mitra Singha.Astrology Consultation Website

About the client

Aparna Mitra Singha is identified by the supplied project as the client. Her website presents her as an astrologer based in Kolkata, West Bengal, practicing within traditions including Vedic astrology, palmistry, and horoscope interpretation. The website describes her services as personalized, compassionate, and oriented toward individual questions about matters such as relationships, career, and life decisions.

These descriptions reflect the site's self-presentation; professional qualifications, duration of practice, predictive efficacy, and independent credentials were not externally established.

Business context

Personalized consultations have a different buying journey from a product catalogue. Before approaching the practitioner, visitors need to understand what the service covers, what information to provide, how the consultation works, and how a reply will be delivered. This particular service is explicitly designed for written-only communication, making the enquiry form and choice of reply channel central to the user experience.

The public page uses English copy alongside Bengali headings, aligning the brand presentation with a Kolkata/Bengal context. This is mixed-language presentation, not evidence of a fully translated bilingual application.

Why this website mattered

The delivered website creates a single destination for visitors to discover the practice, compare its listed services, understand the asynchronous consultation format, and initiate contact. This is the functional opportunity evident from the final site, not an attributed statement about a private client brief or the business's prior performance.

Problem addressed by the delivered experience

The website is organized to reduce several predictable points of friction in a written consultation journey:

• Service ambiguity: Six named offerings distinguish different types of astrological enquiries rather than asking visitors to begin with an unexplained generic message.
• Process uncertainty: A three-step explanation sets expectations around submitting questions, receiving a written reading, and optionally following up.
• Channel preference: Visitors are told they can receive written communication over WhatsApp, Telegram, or email.
• Information collection: The longer form invites birth details and a description of the visitor's specific concern, while a separate short form supports simpler questions.
• Expectation-setting: The FAQ addresses the reply method, information to supply, advertised response times, and confidentiality expectations.

Baseline and scope boundary

No earlier website, manual workflow, design brief, baseline analytics, or documented replacement system was supplied. Accordingly, this is characterized as a website delivery, not a verified redesign, migration, turnaround, or quantified improvement over a prior process.

Important operating constraints visible in the site

• Consultations are advertised as written-only; calls and video meetings are not part of the stated process.
• Some consultation requests may require date, time, and place of birth; these can be personally sensitive details requiring careful handling.
• The visitor may prefer one of three written channels: WhatsApp, Telegram, or email.
• The website advertises a typical reply window of 24–48 hours, with 3–5 days possible for detailed readings. These are site-stated expectations, not independently verified service-level results.
• The site emphasizes confidentiality, but no security audit, storage review, or operational data-handling proof was provided.

Primary objective

Make Aparna Mitra Singha's astrology services easy to understand and straightforward to enquire about, while preserving the website's stated written-only consultation model.

Supporting objectives

• Give the practice a recognizable online identity tied to its owner and Kolkata location.
• Organize the service catalogue into clearly differentiated readings.
• Provide an explanation of the consultation sequence before visitors submit personal information.
• Offer both a detailed request and a lower-friction quick-question route.
• Communicate written reply options and operational expectations transparently.
• Address common visitor questions and present social-proof content visibly on the page.

Observable delivery criteria

The table establishes visible deliverables, not contractual acceptance, conversion performance, or end-to-end integration tests.

Primary users and needs inferred from the product

Prospective consultation clients are the main audience. They may arrive knowing the name of a reading, or they may have a personal question and need help deciding how to ask it. Their practical needs are service clarity, predictable communication, a discreet way to send relevant details, and clear guidance about what happens next.

The practitioner is the operational counterpart. The request forms are designed to organize an incoming enquiry into useful fields before a personalized written response. Whether the form submissions actually arrive in a particular inbox or database was not verified.

Core journey described by the site

1. Discover the practitioner: Read the introduction and understand the written-only format.
2. Choose a service: Browse one of six reading categories or proceed with a general question.
3. Submit a request: Use the full form to supply a preferred service, contact details, optional birth details, and a question—or use the quick-question form.
4. Select written communication: The detailed form asks how the visitor prefers to receive a reply.
5. Receive a response: The site describes a subsequent written consultation and optional follow-up. Fulfilment of this stage was not independently tested.

Product decisions apparent in the final experience

These are observed design choices and reasoned interpretations, not claims about options discussed in an undocumented discovery process.

Public website components

• Hero and introductory positioning: A Bengali/English headline, the practitioner's name, written-guidance positioning, and a prominent personalized-reading request action.
• About section: A short presentation of Aparna's practice and the types of life questions covered.
• Service catalogue: Six reading and guidance categories with their own request actions.
• How It Works: Three stages explaining request submission, written reply, and an optional follow-up.
• Testimonials: Three visitor-facing testimonial entries presented on the public page.
• Written contact section: WhatsApp, Telegram, and email contact choices, plus a shortcut to the quick-question form.
• FAQ: Four answers about receiving a reading, required information, response timing, and confidentiality.
• Detailed consultation request form: A structured intake flow for personal details, desired service, preferred response channel, and the consultation question.
• Quick-question form: A shorter intake asking for name, written contact information, and a question.

Service catalogue

These are categories advertised by the website, not claims that the readings are scientifically validated or a substitute for qualified healthcare, financial, or professional advice.

Detailed enquiry fields visible on the page

Quick-question intake: Name, contact method/address (WhatsApp, Telegram, or email), and question—all shown with required markers.

Delivered destination

Role and attribution

The website is treated here as the client deliverable supplied for this case-study portfolio. The submission identifies Aparna Mitra Singha as the client and provides the public project URL. The visible result supports describing the delivered website experience and its content structure.

A source repository, change history, work log, team roster, and handoff record were not available for this delivery. It would therefore be misleading to claim exclusive authorship of each design decision, implementation of a particular backend, a named delivery schedule, or specific testing achievements.

Contribution demonstrated by the delivered artifact

The table describes demonstrable outputs, not a verified breakdown of the developer's personal responsibilities.

Solution overview

The website acts as a service-explanation and enquiry gateway. It does not require the visitor to understand the practitioner’s process in advance: the visitor can first learn about available readings, then review the written-only workflow, and finally submit a relevant question using either a full or brief form.

The site's greatest differentiator is not a novel astrological technology. It is the explicit productization of a written consultation model: the service format, expected inputs, reply options, and follow-up expectations are presented before the visitor reaches the request form.

Main user experience

First impression: The headline pairs Bengali and English wording, introduces Aparna by name, and makes the request for a personalized reading the central action.

Service exploration: Six service descriptions give visitors a starting point. Individual request buttons are shown with each service, avoiding a purely passive list of offerings.

Process understanding: The three-step explanation makes it clear that submission leads to a written response, not an automatic on-page prediction or a scheduled live meeting.

Detailed request: The main form gathers identity and reply information, desired service, optional birth details, and a free-text question. This structure is appropriate for a practitioner who may need context before composing a response.

Lightweight request: The quick astro question flow reduces the requested information to a name, contact address, and question.

Trust and expectations: The page displays testimonials and answers operational FAQs, including how and when the visitor should expect a response.

What makes the solution fit the described business

A consultation-only service does not need a complex catalogue checkout to explain itself. The implemented information hierarchy puts the practitioner's offering and intake process ahead of extraneous features. The distinct quick and detailed paths create different entry points for visitors with different levels of readiness, while the written-only premise keeps the experience consistent with the business model described on the page.

Capability-to-value mapping

What can be established

The supplied URL is a Netlify-hosted public website. Its rendered content includes service sections, multiple calls to action, FAQs, and two forms with required-field indicators. The public content is sufficient to describe the user-facing information architecture and the intended enquiry workflow.

What is deliberately not asserted

The available evidence does not establish the frontend framework, backend technology, database, form endpoint, webhook service, spam protection, email provider, customer relationship system, analytics, payment gateway, or deployment pipeline. The presence of a form does not by itself demonstrate that entries are saved, transmitted, correctly routed, or delivered successfully.

Similarly, the website states that consultations are confidential, but the review did not include authorization testing, network-traffic inspection, storage-policy inspection, retention verification, or a security audit. No technical privacy guarantee is made in this case study.

Data and communication considerations

The detailed consultation form can solicit date, time, and place of birth together with personal concerns. Those fields warrant a clear privacy notice, limited collection, appropriate access control, secure transmission/storage, and a deletion/retention policy. These are review considerations, not claims that any specific safeguard was or was not implemented.

A separate contact-channel issue is visible in the page content: the public Email contact entry shows hitme@yourakshaw.com. This address should be checked with the client before broader promotion to ensure enquiries reach the intended recipient. The actual delivery and ownership configuration were not independently verified.

Testing and validation scope

The publicly indexed, rendered site content was examined as of 9 November 2026. A live submission of either enquiry form, receipt verification, WhatsApp/Telegram delivery test, responsive-device inspection, accessibility audit, performance benchmark, and security test were not performed for this case-study research. The presence of clickable labels and input fields is therefore recorded as a visible interface, not a confirmed end-to-end operational result.

Site features confirmed in the public review

These are content and interface counts, not traffic, lead, revenue, client satisfaction, or performance metrics.

What was not measured

Delivery duration, project budget, implementation team size, the exact launch date, number of genuine submissions, response completion rate, total consultation bookings, conversion rate, qualified leads, page speed, uptime, retention, and commercial impact were not established. None is assigned a fabricated value.

Verified result

A public-facing, service-led website now makes the written-consultation model discoverable and provides two visible ways for a visitor to begin an enquiry. The website also makes its six offerings, three communication channels, stated turnaround expectations, and common questions accessible in one place.

Business value enabled by the design

• Service clarity: Visitors can distinguish among the listed consultation types before making contact.
• More structured intake: The full form is designed to capture service selection and relevant information within a single request.
• Alternative entry points: The quick form serves people unwilling or unable to complete a longer consultation request immediately.
• Operational expectation-setting: The written-only model and site-stated timing appear before submission.
• Reusable online presence: A directly accessible website provides a destination for links shared through messages, profiles, or other channels.

These are capabilities and plausible benefits, not measured causal improvements.

Results caveats

• No analytics or verified enquiry records were provided, so neither lead volume nor conversion uplift can be claimed.
• No end-to-end form submission was conducted; successful receipt of a reading request remains unverified.
• The website's response-time language is a published promise, not measured turnaround data.
• The three displayed testimonials pertain to the astrologer's services and do not constitute an approved testimonial about this website project.
• The website's confidentiality statements are claims made by the service, not a substitute for security or privacy verification.
• No comparison against an earlier site or workflow was possible; there is no evidence for a before-and-after performance claim.

Review date: 9 November 2026. Website content may change after this observation. The case study intentionally contains no private client messages, fabricated analytics, or invented approval evidence.

Strengths visible in the completed experience

• The operating model is explained early: “Written-only” is part of the service proposition, not a detail hidden until after a booking.
• The intake experience reflects enquiry complexity: A specific reading may require contextual details, while a general question can begin with three fields.
• Service descriptions are structured around visitor intent: The site names and explains several distinct use cases rather than relying solely on the practitioner's biography.
• FAQs carry operational value: Delivery channels and turnaround are stated where prospective visitors can find them before submitting a request.
• Local identity is present: Bengali headings and Kolkata positioning connect the site's presentation to the intended context without requiring an unsupported claim of full localization.

Improvements worth validating before expanding promotion

• Check form delivery in production: Submit controlled test enquiries through both flows and verify routing, error handling, receipt, and duplicate/spam behavior.
• Confirm contact ownership: Ensure the visible email address and WhatsApp/Telegram destinations are the client's intended business channels.
• Validate privacy handling: Review collection, consent, transmission, storage, access, retention, and deletion for birth details and personal questions.
• Confirm testimonial permissions: Verify that all displayed testimonial statements may be used publicly and are correctly attributed.
• Audit mobile and accessibility behavior: Check form labels, error messaging, keyboard navigation, responsive layout, and Bengali text rendering across devices.
• Avoid outcome overpromises: Keep health-related and predictive astrology claims clearly characterized as spiritual or interpretive services, not guaranteed factual or medical outcomes.

These are review recommendations, not defects proven by a full technical audit or commitments already accepted into scope.

Generalizable insight

For personal service businesses, a well-defined service and communication workflow can be more important than adding features. A clear offer, an explicit process, and an intake that matches the service model give prospective clients a coherent next step. The decisive proof of business impact, however, requires actual enquiries and outcome data rather than interface screenshots.

What this project demonstrates

The deliverable demonstrates a coherent information architecture for a niche consultation business: service differentiation, process explanation, two levels of enquiry, response-channel choice, and credibility/FAQ content organized into a public-facing site. It does not, by itself, prove conversion optimization, security certifications, or a particular internal stack.

The items below are recommendations based on the public review, not features represented as delivered or contracted.