Arrow RootBusiness Website
A web presence for Arrow Root, with historical evidence of the contact form delivering visitor messages to an inbox.
Giving Arrow Root a Direct Path for Business Enquiries
Delivered an Arrow Root business web presence with a contact form whose historical test submissions demonstrably reached an email inbox.
AT A GLANCE
- Client
- Bikash Kumar Jaiswal
- Brand
- Arrow Root
- Project category
- Business website with an enquiry form
- Hosting identifier
netlify.appsubdomain (Netlify deployment URL)- Historical functional evidence
- Contact-form notification emails dated 11 November 2025 and 22 June 2026
Overview
Arrow Root is a business website supplied as a completed deliverable for Bikash Kumar Jaiswal. A public trade-directory listing with the same company name and named contact identifies Arrow root as an India-based importer/exporter associated with metal-related trading categories; that possible match is useful context but has not been checked against the deployed site. The strongest direct evidence of the website's functionality comes from historical contact-form tests: messages labelled as Arrow Root website submissions were delivered to a receiving email account on 11 November 2025 and 22 June 2026. That establishes a working historical enquiry-to-email path at the times tested. It does not establish how the current site looks, the technology used, the number of real customers it attracted, or its commercial impact. This case study therefore focuses on what can be substantiated and omits unsupported claims about other features.
Client and Business Context
About the client
Bikash Kumar Jaiswal is the client named for the Arrow Root website project. A public Arrow root trading profile (opens in a new tab) lists a person with this name as its contact and identifies the business as an importer/exporter located in India. The listing associates Arrow root with categories including base metals, brass, iron and steel, metal parts and supplies, precious metals, metal-related equipment, scrap metal, and wire mesh.
The directory record matches both the client name and the Arrow root brand, but it does not link to the supplied Netlify URL. For that reason, its industry and product-category statements should be treated as external business context requiring client verification, not as facts extracted from the website.
The business opportunity represented by the deliverable
For a business that receives potential customer or partner enquiries, a website can provide a recognizable destination for introducing the business and opening direct conversations. The observed Arrow Root contact-form messages show that the project included at least one path from a visitor's enquiry to a delivered email notification.
This is an interpretation of the delivered capability, not a quote from a private discovery brief and not proof that the client previously lacked such a process.
The Starting Point
What can be established
The project is associated with a named client, an Arrow Root website URL, and contact-form notification receipts. Available historical evidence includes multiple test-form notifications across two dates more than seven months apart. That supports the existence of an enquiry workflow at those times, but it does not establish the condition of any earlier website or a redesign process.
The user need addressed by the confirmed feature
The clearest user journey evidenced by the project is straightforward: a visitor provides contact information and a message through a form, and the submission is routed to a mailbox for follow-up. This creates a structured alternative to relying solely on an unformatted email or an off-site social message.
The actual form layout, inline error messages, anti-spam controls, consent text, and current submission backend could not be inspected.
Goals and Success Criteria
Primary objective represented by the confirmed feature
Provide a web-based way for an interested visitor to send an enquiry about Arrow Root.
Evidence-based acceptance criteria
| Criterion | Observed evidence | Assessment |
|---|---|---|
| Identifiable project and destination | Supplied brand, client name and Netlify URL | Project identity provided by client-project owner |
| Visitor enquiry form existed | Historical messages explicitly identify the Arrow Root website contact form as the source | Evidenced historically |
| Form submission could produce an email notification | Test-submission messages were received on 11 November 2025 and 22 June 2026 | Evidenced at the test dates |
| Current site can be opened and visually reviewed | Live-page fetches failed during the 9 November 2026 review | Not verified |
| Real customer enquiries and qualified leads | No production analytics or real-lead records supplied | Not measured |
| Conversion rate, revenue, or time saved | No baseline or outcome data supplied | Not measured |
The table deliberately separates historical feature evidence from current production verification.
User Journey and Product Reasoning
Confirmed enquiry journey
- Open the Arrow Root website. The submitted delivery URL is
https://arrowroot.netlify.app/; a successful live-page load was not reproduced during this case-study review. - Submit an enquiry. Historical form notifications contain fields for name, email, phone, and message.
- Notify the receiving inbox. The historical notifications identified the submission as coming from the Arrow Root website contact form and arrived as email messages.
- Allow human follow-up. The notification format supplies contact details and message content for a recipient to act on; no actual lead response or conversion is documented.
Why the flow is useful
Collecting a structured enquiry can reduce ambiguity about who is contacting the business and what they need. It also makes the contact route available directly from the website rather than requiring visitors to discover a separate platform. These are product-design implications, not measured improvements from the engagement.
Scope and Deliverables
Confirmed delivered elements
| Deliverable | Description | Evidence |
|---|---|---|
| Arrow Root website destination | A client-supplied web deliverable hosted at a netlify.app address |
Project URL supplied with this case study |
| Contact enquiry form | A form collecting visitor name, email, phone and message | Historical contact-form notification content |
| Email notification output | Receiving email messages labelled as Arrow Root contact-form submissions | Inbox records from November 2025 and June 2026 |
Excluded from the documented scope
No claim is made here that the website includes a product catalogue, transactional checkout, inventory management, CMS, user accounts, CRM, multilingual UI, SEO optimization, analytics, chatbot, quote-calculation tool, or payment integration. Such features may or may not exist, but they cannot be confirmed from the accessible evidence.
Delivery Attribution
This project is supplied by Ayush Kumar Shaw as a completed client deliverable for Bikash Kumar Jaiswal. The historical contact-form test messages also indicate hands-on verification activity by Ayush during the project’s existence. They do not establish the full engineering scope, individual code ownership, team size, contract structure, or implementation process.
Accordingly, this case study attributes the project deliverable and the observed testing evidence, rather than assigning unsupported responsibilities such as backend architecture, design leadership, or infrastructure engineering to a particular person.
Solution
Solution overview
The demonstrable solution is an Arrow Root website paired with an enquiry workflow that translates form input into an email notification. It provides a simple mechanism for interested people to supply their details and the reason for contacting the business.
Core capability supported by evidence
Contact-form-to-inbox messaging: Test notifications contain a name, email address, phone number and free-text message, followed by a sentence identifying the source as the Arrow Root website contact form. Receipts on two separate dates show that this notification path operated at the time of those tests.
Before → After, without an invented baseline
| Before | Delivered capability evidenced |
|---|---|
| The pre-project method of handling enquiries is not documented | A website form with a historically functioning email-notification output |
No customer-experience improvement is quantified, because no pre-engagement baseline or user study was supplied.
Technical Implementation
What can be confirmed
- Hosting/deployment URL: The deliverable is identified by a Netlify-hosted subdomain. A Netlify URL identifies its hosting platform, but does not by itself reveal the frontend framework or build system.
- Data captured by the form: Name, email, phone, and message appear in historical notification emails.
- Notification channel: Email messages were received during historical submission tests.
- Testing evidence: Multiple receipts show different form-test values arriving in the mailbox on 11 November 2025 and 22 June 2026.
Technical boundaries
No source repository, deployment configuration, backend implementation, form-handling service, email provider, database schema, anti-spam implementation, authentication design, retention policy, or server logs could be verified. The site was not successfully rendered for this review, so no accessibility, responsiveness, performance, or security score is asserted.
Privacy handling: Form submissions contain personal contact data. The private evidence includes test values; those values are intentionally not reproduced here. A public case study should use redacted evidence or an approved synthetic demonstration instead of exposing mailbox records.
Delivery Evidence and Timeline
| Date | Evidence | What it establishes |
|---|---|---|
| 11 November 2025 | Historical Arrow Root contact-form test notification emails | Email notifications from the form were received on this date |
| 22 June 2026 | Additional Arrow Root contact-form test notification emails | The notification path was exercised again on this date |
| 9 November 2026 | Case-study review of supplied URL, searchable sources and available project records | Site could not be fetched for visual inspection; historical evidence remained available |
These dates are not treated as project kickoff, launch, formal delivery, acceptance, or end-of-maintenance dates. A work schedule and final handover date were not supplied.
Results and Impact
Verified result
A website-associated enquiry-to-email notification workflow was functional during the historical tests. This is the strongest concrete result supported by the evidence.
Business value enabled, but not quantified
The workflow can make inbound conversations easier to initiate and process by placing visitor details and free-text requirements in one message. There is no evidence here that it generated a particular number of business opportunities or sales.
Measurement limitations
- Visitor traffic, qualified leads, lead-to-sale conversions and revenue: Not measured.
- Current site accessibility and current form success rate: Not verified during this review.
- Mobile responsiveness, page speed, SEO rankings and accessibility compliance: Not tested.
- Customer satisfaction, client testimonial, or post-launch feedback: No approved evidence supplied.
- Historical delivery tests: Evidence of notification delivery, not proof of current operation or real-customer conversion.
Proof and Source Register
| Source | Evidence supported | Access / confidence |
|---|---|---|
| Supplied Arrow Root website (opens in a new tab) | Project identifier and intended public destination | Supplied by project owner; direct site inspection unavailable on 9 November 2026 |
| Historical contact-form notification emails dated 11 November 2025 | Form submission fields and email-notification delivery | Private mailbox records; high confidence for historical receipt only |
| Historical contact-form notification emails dated 22 June 2026 | Repeated testing of the form-to-email notification path | Private mailbox records; high confidence for historical receipt only |
| Arrow root profile on Exporters.SG (opens in a new tab) | Brand and contact-name match; India-based importer/exporter listing, metal-related categories | Third-party profile; match to this exact site not independently established |
The third-party listing is not evidence of website content, an implemented product catalogue, legal status, completed trade transactions, or commercial performance.
Lessons and Reflection
What this project demonstrates from the available proof
The deliverable had more than a static URL: at least one website-to-inbox interaction was exercised and produced tangible evidence in an email inbox. A functioning enquiry route is a meaningful building block for a business website, even without a full sales workflow.
Generalizable insight
A deployed website and a completed commercial outcome are different claims. A received test email proves a historical notification path worked; it does not prove the current production flow is healthy, that customers submitted enquiries, or that the business generated additional revenue. Useful case studies draw that boundary explicitly.
See all case studies