business-consultant

byDebashish Sen

Website for Debashish Sen as a Business Consultant and Advisory Services

LandingServicesContactProfile
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Debashish Sen

1. Introduction

This System Requirements Document defines the website for Debashish Sen, a business consultant offering advisory services. The product is a public, first-party website that presents Debashish Sen and his business consulting and advisory services to prospective clients, and gives those visitors a way to contact him about an advisory engagement.

The audience is twofold. Prospective clients — leaders and business decision-makers looking for a consultant — arrive to understand who Debashish Sen is, what advisory services he offers, and how to start a conversation. Debashish Sen is the consultant whose profile and services the site presents so that prospective clients can reach him.

The site is a presentation-and-contact product: it explains the consultant, his audience, and his advisory services, and it lets a visitor make contact. It is not a client portal, booking system, or content-management product.

2. System Overview

Page 1 of 18

2a. Product Interpretation and Delivery Boundary

The product is a public marketing and contact website delivered as a first-party React application backed by a shared FastAPI service and a MariaDB database. All four accepted pages — Landing, Profile, Services, and Contact — are publicly reachable with no access requirement; there is no sign-in, account, or gated area. The visitor reaches the public Landing page at the root.

The site's current scope is exactly what the source accepts: present Debashish Sen and his business consulting and advisory services, and let a prospective client contact him about an advisory engagement. The Contact page collects the visitor's enquiry and delivers it to Debashish Sen; the shared backend persists the enquiry so it is not lost, and the database holds that application-owned data. No other product capability — scheduling, payments, client dashboards, testimonials management, or content authoring — is part of the current delivery.

Everything the site presents is authored content about the consultant and his services. The site does not invent biography, credentials, pricing, or service claims beyond what is supplied as content; where the source does not specify a detail, it is treated as content to be supplied rather than a new feature.

2b. Source Content Inventory

The authoritative sources do not supply verified factual content (biography text, service names, contact details, or media) for Debashish Sen. No content inventory is asserted here; page content is defined structurally in 2c and populated from the consultant's supplied material.

2c. Page Content and Component Coverage

Page 2 of 18

Landing

  • Information / state: The public entry at the root. Presents Debashish Sen as a business consultant and the advisory services he offers, and orients the visitor toward the Profile, Services, and Contact pages. Hero copy: headline "Clear advice for hard business decisions"; subline "Debashish Sen gives business consulting and advisory services to leaders who need a plan they can act on."; call to action "Start a conversation".
  • Primary actions: Follow the hero call to action to Contact ("Start a conversation"); navigate to Profile and Services.
  • Supporting actions: Navigate to any other page via the site navigation.
  • Domain entities: Consultant identity (Debashish Sen), advisory service summary.
  • Component responsibilities: Split hero (paper half with headline, burnt-orange rule, and CTA; ink half with monospace advisory note and thin orange diagram line); section openers alternating sides of the grid with square markers and hairline rules; a service summary list rendered as label/value rows in monospace numerals on the ink panel; site navigation.
  • States: Loading — static content, no spinner required; Empty — not applicable (content is authored); Success — hero and sections render fully; Error — if content fails to load, the page shows the navigation and a plain fallback message rather than a blank screen; Recovery — reload restores the page.
Page 3 of 18

Profile

  • Information / state: The profile of Debashish Sen as a business consultant — who he is and the perspective he brings to advisory work, drawn from supplied content.
  • Primary actions: Read the profile; proceed to Services or Contact.
  • Supporting actions: Navigate via site navigation.
  • Domain entities: Consultant profile.
  • Component responsibilities: Profile narrative in body type; section openers with square marker and hairline rule; a link onward to Services and Contact.
  • States: Loading — static content; Empty — if profile content is unavailable, show a short placeholder line and keep navigation usable; Success — profile renders; Error — fallback message with navigation intact; Recovery — reload.

Services

  • Information / state: The business consulting and advisory services Debashish Sen offers, presented as a list of services.
  • Primary actions: Read the service list; proceed to Contact to start a conversation about a service.
  • Supporting actions: Navigate via site navigation.
  • Domain entities: Advisory service (name and description).
  • Component responsibilities: Service list as label/value rows in monospace numerals on the ink panel; each row flips its half from paper to ink on hover with a 160 ms colour swap; section openers with square marker and hairline rule; a link onward to Contact.
  • States: Loading — static content; Empty — if no services are supplied, show a plain message and keep Contact reachable; Success — service rows render; Error — fallback message with navigation intact; Recovery — reload.
Page 4 of 18

Contact

  • Information / state: A way for a prospective client to contact Debashish Sen about an advisory engagement. Presents an enquiry form capturing the visitor's name, email address, and message.
  • Primary actions: Submit the enquiry form.
  • Supporting actions: Read confirmation after submission; return to other pages.
  • Domain entities: Enquiry (name, email, message, submitted timestamp).
  • Component responsibilities: Enquiry form with labelled fields (name, email, message) and a submit control; inline validation messages; success confirmation; error message with retry.
  • States: Loading — submit control shows a pending state while the enquiry is sent; Empty — form fields start empty with labels and no pre-filled values; Success — a confirmation message tells the visitor the enquiry was sent to Debashish Sen; Error — if submission fails, the form retains the entered values and shows a retry message; Recovery — the visitor can resubmit.
Page 5 of 18

3. Functional Requirements

FR-1 — Public website presenting the consultant and services (explicit) As a prospective client, I should reach a public website that presents Debashish Sen as a business consultant and his advisory services, so that I can understand what he offers.

  • Trigger/input: The visitor opens the site root.
  • Observable result: The Landing page renders with the consultant's identity, hero copy, and orientation toward Profile, Services, and Contact.
  • Access state: Public, no sign-in.
  • Failure/recovery: If content fails to load, navigation and a fallback message remain; reload recovers.
  • Continuation: The visitor navigates to Profile, Services, or Contact.

FR-2 — Read the consultant's profile (required_inference) As a prospective client, I should read the profile of Debashish Sen as a business consultant, so that I can judge whether his perspective fits my situation.

  • Trigger/input: The visitor opens Profile.
  • Observable result: The profile narrative renders.
  • Access state: Public.
  • Failure/recovery: If profile content is unavailable, a placeholder line shows and navigation stays usable; reload recovers.
  • Continuation: The visitor proceeds to Services or Contact.
Page 6 of 18

FR-3 — Read the advisory services (required_inference) As a prospective client, I should read the business consulting and advisory services Debashish Sen offers, so that I can identify the service relevant to my need.

  • Trigger/input: The visitor opens Services.
  • Observable result: The service list renders as label/value rows; hovering a row flips its half from paper to ink within 160 ms.
  • Access state: Public.
  • Failure/recovery: If no services are supplied, a plain message shows and Contact stays reachable; reload recovers.
  • Continuation: The visitor proceeds to Contact.

FR-4 — Contact the consultant about an engagement (required_inference) As a prospective client, I should contact Debashish Sen about an advisory engagement, so that I can start a conversation.

  • Trigger/input: The visitor opens Contact and submits the enquiry form with name, email address, and message.
  • Observable result: The enquiry is accepted by the backend, persisted, and delivered to Debashish Sen; the visitor sees a confirmation.
  • Access state: Public.
  • Failure/recovery: If submission fails, the form retains entered values and shows a retry message; the visitor can resubmit.
  • Continuation: The visitor sees confirmation and may return to other pages.
Page 7 of 18

FR-5 — Receive and review enquiries (required_inference) As Debashish Sen, I should receive the enquiries prospective clients submit, so that I can respond and begin an engagement.

  • Trigger/input: A prospective client submits the Contact form.
  • Observable result: The enquiry (name, email, message, submitted timestamp) is stored by the shared backend and made available to Debashish Sen for review.
  • Access state: The enquiry is application-owned data; it is not exposed on any public page.
  • Failure/recovery: If storage fails, the visitor sees the retry state from FR-4 and no partial enquiry is presented as received.
  • Continuation: Debashish Sen reviews the enquiry and follows up with the prospective client outside the site.

4. User Personas

Page 8 of 18

Prospective client

  • Product context: A leader or business decision-maker looking for a business consultant and advisory services. They arrive at the public site without an account and evaluate whether Debashish Sen is the right advisor.
  • Primary goal: Understand who Debashish Sen is and what advisory services he offers, then make contact to start an engagement.
  • Distinct accepted responsibilities: Reads the Landing page, reads the Profile, reads the Services list, and submits an enquiry on Contact.
  • Relevant inputs or decisions: Decides whether the consultant's perspective and services fit their need; decides to start a conversation.
  • Interactions with other accepted participants: Their submitted enquiry is received by Debashish Sen.
  • Observable success: They reach Contact, submit a valid enquiry, and see a confirmation that it was sent.
Page 9 of 18

Debashish Sen

  • Product context: The business consultant and advisory services provider whose profile and services the site presents. He is the subject of the site and the recipient of enquiries.
  • Primary goal: Present his profile and services so that prospective clients can understand his offering and contact him.
  • Distinct accepted responsibilities: Supplies the profile and service content the site presents; receives and reviews enquiries submitted by prospective clients.
  • Relevant inputs or decisions: Reviews each enquiry's name, email address, and message to decide how to follow up.
  • Interactions with other accepted participants: Receives enquiries from prospective clients.
  • Observable success: Enquiries from prospective clients are stored and available to him for review, and he can follow up.

5. Core User Flows

Page 10 of 18

Flow A — Prospective client evaluates the consultant and makes contact

  1. The prospective client opens the site root and lands on Landing. They see the headline "Clear advice for hard business decisions", the subline describing Debashish Sen's advisory services, and the call to action "Start a conversation".
  2. They open Profile from the navigation and read Debashish Sen's profile as a business consultant. Result: they understand his perspective. Failure: if profile content is unavailable, a placeholder line shows and navigation stays usable; they can continue to Services.
  3. They open Services and read the advisory service list as label/value rows. Hovering a row flips its half from paper to ink within 160 ms. Result: they identify the service relevant to their need. Failure: if no services are supplied, a plain message shows and Contact stays reachable.
  4. They open Contact (or follow "Start a conversation" from Landing) and complete the enquiry form with their name, email address, and message.
  5. They submit the form. Result: the backend accepts and stores the enquiry and the visitor sees a confirmation that it was sent to Debashish Sen. Failure: if submission fails, the form retains the entered values and shows a retry message; the visitor resubmits.
  6. Continuation: the visitor may return to any page; their enquiry is now with Debashish Sen.
Page 11 of 18

Flow B — Debashish Sen receives and reviews an enquiry

  1. A prospective client submits the Contact form (Flow A, step 5).
  2. The shared backend stores the enquiry with the visitor's name, email address, message, and submitted timestamp.
  3. Debashish Sen reviews the stored enquiry. Result: he has the visitor's name, email address, and message to act on.
  4. Continuation: Debashish Sen follows up with the prospective client outside the site to begin the engagement.
Page 12 of 18

6. Visuals Colors and Theme

The creative direction — dual-nature craft after Adham Dannaway, headline "Clear advice for hard business decisions" — is authoritative for this section.

Mode: Light mode as the primary mode.

Colour tokens (exact hex by role):

  • Background (warm paper ground): #F4F1EA
  • Surface: #FFFFFF
  • Text (ink): #14161A
  • Primary: #14161A
  • Accent (burnt orange): #D9481F
  • Muted: #6B6F76
  • Dark ink panel (technical half): #14161A

Warm paper covers most of the area; ink text and the single burnt-orange accent carry all emphasis; the dark ink panel holds the technical half.

Typography:

  • Headings: Space Grotesk, weight 500, tight tracking, sentence case, short lines, large sizes.
  • Body: Newsreader.
  • Scale: 1.333 modular — 64 / 48 / 32 / 22 / 17 / 15, with clamp() from 40px on mobile to 96px on desktop for display headings.
  • Monospace notes and numerals on the ink panel use a monospace family.

Shape language: Sharp corners; precise 8-pt spacing; thin hairline rules divide the two halves; small square markers label each section.

Page 13 of 18

Layout: A split first screen — left half paper with ink type, right half an ink panel with monospace notes. Sections alternate sides on a strict 12-column grid.

Imagery style: Schematic diagrams and ruled notes over soft photography; product shots show half wireframe and half finished form.

Avoid: No gradient blobs or glass panels; no blue or indigo accent; no rounded pill buttons or soft drop shadows; no stock photos of handshakes or boardrooms; no centred hero with a subtext and a blue button.

Readability constraint: Headlines, wordmarks, labels, numbers, and card text and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (e.g. clamp()) to fit; no other element covers any part of them. Imagery and decoration may be cropped or bled off edges; readable text and controls may not.

7. Signature Design Concept

The public entry (Landing) is built on a 50/50 split hero. The left half is warm paper (#F4F1EA) holding an oversized ink headline — "Clear advice for hard business decisions" — stacked over a burnt-orange rule, with the "Start a conversation" call to action beneath it. The right half is a dark ink panel (#14161A) carrying a white monospace advisory note and a thin orange diagram line, evoking a ruled working note beside a finished plan.

Below the hero, section openers alternate sides of the 12-column grid, each carrying a small square marker and a hairline rule. The service list on Services renders as label/value rows in monospace numerals on the ink panel; hovering any service row flips its half from paper to ink with a 160 ms colour swap. The concept recomposes only accepted content and controls — the hero copy, the CTA, the service list, and navigation — and introduces no new behaviour or destination.

Page 14 of 18

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: layered_2d

Landing Hero Motion Brief

  • Focal subject: The split first screen — paper half with the oversized ink headline and burnt-orange rule, ink half with the white monospace advisory note and thin orange diagram line.
  • Input → transformation → outcome thesis: As the visitor moves across the split, the two halves reveal in dialogue — the paper half and ink half respond to hover with a slow parallax between them, and the burnt-orange rule and diagram line draw attention to the CTA — so the visitor reads the headline, the advisory note, and "Start a conversation" as one composed statement.
  • Motion vocabulary: Reveal by hover across the split; slow parallax between halves; all transitions run in 160 ms with no bounce.
  • Composed first frame: Left half paper with the ink headline stacked over the burnt-orange rule and the CTA; right half ink panel with the monospace note and thin orange diagram line; hairline rule dividing the halves; square marker at the section opener.
  • Reduced-motion state: With prefers-reduced-motion, the parallax and hover reveals are disabled; the split renders as a static two-half composition with all text and the CTA fully visible and usable, and any content that would move wraps or scrolls so each item can be brought fully into view.
Page 15 of 18

9. Non-Functional Requirements

  • Public access: All four pages (Landing, Profile, Services, Contact) are publicly reachable with no sign-in or account. (explicit — access requirement none for every surface)
  • Readability across viewports: Readable text and controls stay whole and inside their container at 375px, 768px, and 1280px, wrapping or scaling to fit; no element covers them. (explicit — user design constraint)
  • Reduced motion: A usable static arrangement is provided under prefers-reduced-motion, with moving or scrollable content wrapping or scrolling so each item can be brought fully into view. (explicit — user design constraint)
  • Enquiry durability: Submitted enquiries are persisted by the shared backend so they are not lost between submission and review. (required_inference — supports FR-4/FR-5)
  • Enquiry privacy: Stored enquiries are application-owned data and are not exposed on any public page. (required_inference — supports FR-5)
  • Form validation: The Contact form validates that name, email address, and message are present and that the email address is well-formed before submission, showing inline messages. (required_inference — supports FR-4)
  • Performance and motion discipline: Transitions run in 160 ms with no bounce, per the creative direction. (explicit — creative direction)
Page 16 of 18

10. Tech Stack

  • Frontend: React application UI. (provisioned scaffold)
  • Backend: Shared FastAPI process for application APIs and domain modules, including the enquiry submission endpoint. (provisioned scaffold)
  • Database: MariaDB for application-owned persistent data, holding submitted enquiries. (provisioned scaffold)
  • Containerization: docker-compose.yml with the frontend, backend, and database services as the runnable inventory. (provisioned scaffold)

11. Assumptions and Constraints

  • Content is supplied, not invented: Profile narrative, service names and descriptions, and contact routing details are supplied content; the site does not fabricate biography, credentials, pricing, or service claims. (assumption)
  • No accounts or gated areas: Every page is public; no authentication, client portal, or differentiated permissions exist. (explicit — access requirement none)
  • Enquiry delivery: The enquiry is stored by the shared backend and made available to Debashish Sen for review; the specific review mechanism is an implementation detail of the backend and does not add a public page. (required_inference)
  • Follow-up is off-site: Debashish Sen's response to an enquiry happens outside the website; the site does not provide a messaging or scheduling capability. (assumption)
  • Design direction is binding: The palette, fonts, split layout, sharp corners, and motion tempo in Sections 6–8 are fixed by the creative direction and user design constraints. (explicit)
Page 17 of 18

12. Glossary

  • Advisory engagement: A consulting relationship a prospective client seeks to start by contacting Debashish Sen.
  • Advisory service: One of the business consulting services Debashish Sen offers, presented on the Services page.
  • Enquiry: A message submitted through the Contact form, comprising the visitor's name, email address, and message, with a submitted timestamp.
  • Ink panel: The dark #14161A half of the split layout that holds monospace notes and the service list.
  • Paper half: The warm #F4F1EA half of the split layout that holds ink headlines and the call to action.
  • Prospective client: A visitor evaluating Debashish Sen's advisory services and potentially making contact.
  • Split hero: The 50/50 first-screen composition dividing paper and ink halves.
Page 18 of 18
Live
Landing design preview
Landing: Review presented identity and hero
Profile: Review supplied profile narrative
Services: Review supplied service list
Contact: Review enquiry form fields
Contact: Receive stored enquiry
Contact: Review name, email, message
Contact: Follow up outside site
Live
Landing design preview
Landing: Review presented identity and hero
Profile: Review supplied profile narrative
Services: Review supplied service list
Contact: Review enquiry form fields
Contact: Receive stored enquiry
Contact: Review name, email, message
Contact: Follow up outside site