Cover title.
Two documents. The audit came first and on its own, written from the outside and from your own process document, before any build work was discussed. The proposal exists because you read it and asked what could be done. They are meant in that order, though either stands up alone.
No analytics, no admin login, no inbox, no CRM. Everything below was visible to anyone who cared to look, plus the one internal document you handed us. If we could see it, so can a CHRO's procurement team, a search engine, and the next person deciding whether to hand you their leadership team for four days in a tiger reserve.
What we examined
Everything public, read as raw markup rather than as a rendered page.
| Pass | What it covered | Method |
|---|---|---|
| The public site | Homepage, About Us, Corporates, Schools, Private Tours, Destinations, Our Events, Contact Us, Blog, News and Media, the shop and individual product pages | Fetched and read as source |
| The legal layer | Terms and Conditions, Privacy Policy and Shipping & Returns Policy, in full | Read clause by clause and cross-checked against each other and against what the site sells |
| The machine surface | Titles, descriptions, canonicals, social cards, publication and modification dates, plugin fingerprints | Read as metadata, not as a page |
| The channels | The four accounts linked in your own footer, and the ones that exist but are not linked | Observed from outside |
| Your process document | The Business Process Flow: two journeys, thirty-one steps | Read as the operating specification it is. The only non-public thing here, and it is marked wherever it is used |
What we could not see
Stated up front, because a report that hides its own limits is not worth much.
| Your analytics | Traffic, sources, enquiry volume, which of the seven enquiry routes actually carries the load. None of it public. Where a number would help, we say so rather than estimating one. |
| The follow-up rule | Your process document says a follow-up fires automatically when the expected turnaround passes. Whether that runs on its own or is somebody remembering is the difference between a process and an intention, and we could not tell from outside. |
| Where the enquiries land | The QR code, the WhatsApp thread and the Kenya form all terminate somewhere we cannot follow. We can count the doors. We cannot see the room. |
| The entity | No CIN, GST number, or Pvt Ltd, LLP or proprietorship suffix appears anywhere public. We are not saying one does not exist. We are saying nothing on the site or in the public record told us. |
| Your economics | The ₹2.5 crore FY24 figure is from your own press coverage. How it splits across corporate, private tours, schools and the shop is not public, and that split changes which of the findings below matters most. |
| Load and performance | Not measured. WordPress carrying Slider Revolution, WooCommerce, Download Manager and a Meta Pixel is a heavy stack, but that needs a run from a real device on a real network before anyone says so. |
The most useful thing we found is not a problem. It is a date.
Core zones at Corbett, Tadoba, Kanha, Bandhavgarh and Pench close on 1 July and reopen on 1 October. Kaziranga opens later still, in stages through October and November. Nothing in this report has to be finished by then. What changes on that date is what each item costs to deal with. Today is 31 August, so the answer is about thirty days.
The operating year
Eight months of delivery, four months of everything else. This is the four.
Two of your four quiet months have already gone. September is the whole of the remaining window, and it is the only stretch of the year in which nobody is in a forest, on a flight, or writing a proposal against a date.
Why this report is ordered by reversibility rather than severity
Most audits hand you a list of problems sorted by how bad each one is. For a seasonal business that is the wrong sort, because severity does not move and your capacity to act does. A serious problem you can address in any week of the year deserves less of your attention right now than a small one that hardens on a date you do not control.
So the findings that follow are not ranked by damage. They are ranked by what the first of October does to them. It does three different things, and separating them is the point of this section.
The three things October does to a problem
Every finding in sections 03 to 08 belongs to one of these. The class is what determines the order, not the size.
| Class | What the season does to it | Where you will meet it |
|---|---|---|
| Exposure | The fault does not get worse. The number of people who meet it does. A legal page describing a different business is exactly as wrong in February; what October changes is how many procurement teams, legal reviewers and first-time buyers read it before deciding. | 04 · The trust layer 06 · Being found |
| Attention | The fix stays the same size and the room to make it disappears. From October the people who would make the change are delivering programmes or quoting the next one. A half-hour edit stops being a task and becomes an interruption, and interruptions get deferred to the following July. | 03 · The public surface 05 · The process |
| Record | Nothing breaks and nothing is fixable afterwards. These are not faults at all; they are things that are only ever captured while they are happening. A season passes through the gap and leaves no trace of itself. | 05 · The process 07 · The channels |
The third one is the one to weigh first
Exposure and attention are both arguments about cost. Something is dearer to handle in December than in September, and reasonable people can decide to pay the difference.
Record is not an argument about cost. Enquiries arriving across seven unconnected routes are not lost, exactly. Most of them get answered. What is lost is the answer to "where did this season's business come from", and that answer cannot be reconstructed in June. The same applies to which proposals converted, which follow-ups went out on time, and what participants said in the week after a programme rather than six months later.
Every season that runs without that record is a season you cannot learn from. It is the only class of finding here where waiting does not make the work harder. It makes the work impossible, and you would not know what you were missing.
- Core zone and buffer zone
- The core is the protected heart of a reserve, closed to tourism from 1 July to 30 September. Buffer zones on the edges often stay open year-round, which is why some safaris run in the monsoon, but not the ones a corporate offsite is built around.
- Shoulder months
- The weeks either side of a season, when nobody is travelling but everybody is deciding. For you that is September, and to a lesser extent July and August. It is when the selling and the fixing both have to happen.
Nothing here is an emergency, and a park reopening does not cause a legal problem or a broken form. The date is not a threat. It is a price list. It tells you what each of the findings that follow will cost to deal with depending on when you get to it, and in one case that there is no later.
A naturalist and an HR facilitator running leadership work in a tiger reserve, priced as L&D rather than as travel, is a sharp and defensible position, and almost nobody else has it. What is unfinished is not the pitch. It is the eight or nine small things a buyer meets before they reach it.
What is working
More than the surface suggests, and worth saying before the rest.
The team page is the strongest asset on the site, and it is buried
The workshop pages are structured the way a buyer needs
The testimonials are real, named and titled
The press coverage is real, and it is business press
The delivery evidence is strong where it exists
The shop is more thoughtful than it needs to be
Loose ends worth clearing
Each is more visible to a first-time visitor than its size suggests.
The rating widget opens with an empty box rather than with 4.69
Every workshop is rendered twice on the same page
Both hero buttons say EXPLORE and go to different places
The homepage says it was published in February 2020
Your own metadata advertises the homepage as an 81-minute read
The copyright year disagrees with itself
Small spelling errors sit on the pages that build trust
Pages the site still needs
Not a redesign. Four pages that do not exist and are being asked for anyway.
Anything at all about price
A cancellation and refund page for trips
A departures or season page
An outcomes page for the buyer who has to justify it
None of the above is a redesign. All of it is content that already exists inside the business and has not been written down on the site.
This is the most serious section in the audit and also the cheapest to fix. Nothing here requires a decision about strategy. It requires three documents to be replaced by three documents that describe the business you actually operate. All of it gets much harder once someone has already relied on it.
The Privacy Policy belongs to a cake shop
Three links in the published page still point at the site it was copied from.
Scope paragraph text reads www.wildlifewhisperers.com, link points to kimcakecreation.com
Dispute resolution displays info@wildlifewhisperers.com, mailto resolves to info@kimcakecreation.com
Final contact displays info@wildlifewhisperers.com, mailto resolves to info@kimcakecreation.com
Grievance Officer not named anywhere in the document
DPDP Act not referenced anywhere in the document
Retention periods none stated
Why this is the first thing to fix, ahead of everything else in this report
The invisible half matters more. This policy is the only statement you make about personal data, and you collect a great deal of it: passport and visa details for Kenya, Sri Lanka and Nepal, dietary and medical information for jungle stays, participant rosters for corporate clients, and payment data through WooCommerce. It names no Grievance Officer, which the DPDP Act requires; refers the reader to a Privacy Officer using "the contact information above", which does not appear above; states no retention periods; and describes none of the data categories a travel business actually handles.
The exposure is not theoretical and it is not with consumers. It is with the first corporate client whose legal or infosec team reads your privacy policy as part of vendor onboarding, which is a routine step, and exactly what happens when a company sends twenty employees abroad with you.
- DPDP Act
- India's Digital Personal Data Protection Act, 2023. The national law covering how organisations collect and handle personal data. It applies to you because you collect identity documents from individuals in India.
- Grievance Officer
- A named, contactable person a customer can complain to about their data. Indian law requires the name and contact to be published. It can be Sai Kiran. It cannot be nobody.
- Vendor onboarding
- The checks a large company runs before paying a new supplier: legal entity, tax registration, insurance, data handling. Perfetti Van Melle will have run one on you already. The next client will too.
The only cancellation route you publish does not exist
One character, on the one page a customer reaches when something has gone wrong.
"…please send an email to info@wildlifewhisperer.com, including your order number"
The domain is wildlifewhisperers.com. The address published here is missing the s.
Every other mention of the address on the site is correct, so this is a typo rather than a system. It is also the single instruction given to a customer trying to cancel, and it silently fails. Nobody who has tried to use it has been able to tell you it does not work.
Which company, and where
The Terms describe a business in a different city, with no legal form.
Jurisdiction clause "Wildlife Whisperers is controlled and operated from Bangalore, India"
Registered address, everywhere else 21-100, 9th Cross, Uttam Nagar, Hyderabad 500047
Legal form no Pvt Ltd, LLP, proprietorship or partnership named anywhere public
CIN not published
GSTIN not published, on a site that sells physical goods
The word "concern" is doing a lot of work here
We are not asserting that no registered entity exists. We are reporting that nothing public tells a buyer what it is. For a business turning over ₹2.5 crore and selling to multinationals, the absence is itself the finding. A GST invoice, a PAN and a legal name are the first three things a procurement portal asks for, and none can be confirmed from your site before a buyer picks up the phone.
What your Terms actually cover
Read against what you sell. Eight things that can go wrong on a trip, and what the contract says about each.
The pattern is consistent: the legal layer describes an online print shop, and the print shop is the smallest thing you do. The Terms were last modified in July 2024 and the Privacy Policy in November 2023, which is roughly when the business stopped being what those documents describe.
- Force majeure
- The clause that says what happens when something outside anyone's control stops the trip: a park closing, a flood, a flight ban. Without it, who absorbs the cost is decided by argument rather than by agreement.
- Assumption of risk
- The participant's written acknowledgement that a jungle is a jungle. Standard in adventure travel worldwide, absent here.
This section needs a lawyer, not us
Three items sit outside what we can advise on: the entity and its tax registration, the DPDP position and the appointment of a Grievance Officer, and the travel terms themselves. What we can say is that all three are documents rather than decisions, that a specialist travel-terms template is a few days of work, and that the cost of doing it in September and the cost of doing it in January are the same. Only the exposure in between differs.
Your Business Process Flow is the closest thing the business has to a specification, and it is better than most companies your size have written down. It is also the thing any CRM will be built to mirror. Whatever is missing from it now will be missing from the system afterwards, and will cost a change request rather than a conversation.
The journeys as written
Solid blocks are steps your document defines. Dashed blocks are the stages it does not have.
B2C opens at an in-person meeting, so everything that produces the meeting sits outside the process. Both journeys end at feedback, so nothing goes back to the buyer. And neither has a branch for the booking that moves. Those dashed blocks are the pipeline stages a CRM will not have unless they are written first.
What the document gets right
Two journeys, correctly separated
The pre-trip sequence is date-driven, not mood-driven
The B2B path knows what it is selling
There is a turnaround rule
What is missing from it
No cancellation, reschedule or refund path
No lead generation stage before B2C step 1
No payment receipt or reconciliation tracking
No post-workshop impact report
Vendor and property management is undocumented
Schools and the shop are not covered at all
Seven ways to reach you, and no way to count them
Every one of these works. None of them meets any other.
Keep every front door. The QR code, the WhatsApp thread and the Kenya form all work and people use them. What is missing is the room they open into, which is why the question "where did last season's business come from" currently has no answer.
The enquiry form only fits one of your four businesses
Read as a form rather than as a page.
Interested In required · Teamwork · Leadership · Business Excellence · Decision Making · Mental Health
Business Excellence The Lion King, marked Coming Soon on the homepage
Decision Making Eye of the Tiger, marked Coming Soon on the homepage
No option for a private safari, a school programme, a print, or anything else
What this form does to a private traveller in October
Two of the five options sell workshops that do not exist yet, and a buyer who selects Business Excellence receives a reply explaining that it is coming soon. The Corporates page lists only three workshops, so the form and the catalogue disagree about what you sell.
This is a fifteen-minute fix and it is the highest-yield fifteen minutes on the site. Add an audience question first, corporate, private, school or shop, and branch from there. Everything downstream, including the CRM pipelines, depends on knowing which of the four businesses an enquiry belongs to, and right now that is inferred from prose.
Every page is titled, described and indexed for nature immersion, mindfulness and workshops in Hyderabad. The revenue engine is multi-day corporate offsites in national parks, sold to CHROs, delivered in Corbett, Tadoba, Kabini, Kaziranga and Kenya. Almost none of that appears in the metadata.
What a machine sees
Not a summary. This is the metadata as published, on the two pages that matter most.
Homepage description Escape the urban rush with nature immersive sessions in Hyderabad. Guided outdoor activities designed for relaxation, healing, and mindfulness.
Corporates title Corporate Trainings in Hyderabad for Professional Growth
Corporates description Empower your workforce with top corporate training in Hyderabad. Unlock leadership, communication, and team-building skills with expert trainers.
Homepage published 2020-02-26 (company founded 2023)
Homepage read time, as published 81 minutes
Generator Slider Revolution 6.6.16 · Download Manager 5.0.21 · WooCommerce · Meta Pixel
The Corporates page describes generic corporate training delivered by expert trainers. That is the one category where you have no advantage and hundreds of competitors. The differentiator, the jungle, is absent from the metadata of the page that sells it.
Findings, in the order they cost you
No price exists anywhere on the site
Positioned for Hyderabad, delivered across India and Africa
Our Events is an archive, not a calendar
No structured data for events, courses or products
Two Facebook pages, one linked
Duplicate workshop content on the Corporates page
The blog is dated 2023, and News omits the business coverage
Being answered, not just indexed
Increasingly the CHRO does not search. They ask an assistant to find corporate offsite providers who run leadership programmes inside Indian national parks, and they get three names with rough prices and durations attached.
You are unusually well placed to win that and currently cannot. The workshop pages are the strongest asset you have here: duration, minimum batch size, recommended audience and structured outcomes are exactly the fields an assistant needs to compare you against alternatives. Three things are missing: a price band, the destinations each workshop runs in, and the months it is available. All three exist in Sai Kiran's head and in the rate card you send by email.
Sai Kiran's LinkedIn is doing the work that a company page, a content calendar and a sales team would do elsewhere, and it is doing it well. The brand accounts are largely a mirror of the website, and two of them are not in your own inventory.
Where each stands
Green is working. Amber is passive. Red needs a decision.
LinkedIn · personal
The real distribution channel. Regular long-form posts on wellness, digital fatigue and psychological safety, plus speaking invitations. This is where the B2B pipeline starts.
LinkedIn · company
Exists. Not the account doing the work.
Instagram · brand
~994 followers, ~118 posts. The homepage gallery is this feed, so the site and the account say the same thing.
Instagram · photography
Supplies most of the site's imagery and is credited in every footer. Larger reach than the brand account, and not positioned as the founder's.
Instagram · co-founder
Vaibhav Peri. Not linked from the site, and Vaibhav does not appear on the team page at all.
The footer points at one; /wildlifewhisperers.ind sits at 74 likes. One of them should be merged or closed.
YouTube
Linked in your own footer on every page and absent from your internal channel list. Worth checking what is on it before anyone plans around it.
X and Threads
Both are named in the publishing tool you have asked for, so the tool would be scheduling into two empty rooms.
The instinct to lead with the founder has been right. In a category built on trust, and you are asking a company to put its leadership team in a forest for four days, a named person with a photography portfolio and a Deloitte-credentialled advisor is worth more than a brand account posting tiger photographs.
The problem is not the strategy. It is that the strategy currently has one throat. Sai Kiran writes the posts, takes the photographs, answers the enquiries, quotes the price and runs the programme. Anything built here should reduce the number of those five he has to keep doing in October, and publishing to two accounts that do not exist yet is not on that list.
The category around you splits cleanly in two: travel companies who can run a safari and cannot design a leadership programme, and L&D firms who can design one and deliver it in a hotel. You are the only credible thing in the middle, and the site does not say so.
Where you actually sit
Two capabilities, four boxes. Only one of them has anybody in it.
Where the position is genuinely strong
The pairing is the product
Dimple Agarwal is a category-defining credential
The revenue is the proof
The destination range is a real moat
The honest version
The offer is unpriced and undated, so every deal is bespoke
The season is eight months long and capacity is finite
Two revenue lines have no structure at all
The competitor is not who you think
Nothing below needs a new website, a new tool, or a decision about the platform. It is the list of things that are cheaper this month than next. Tick them off as they land. The first group is a week of somebody's attention.
Before the gates open
Seven items, all of them September work. This list is interactive.
Then, in order
Before the season peaks
- Publish a price band. From ₹X per participant, minimum batch, typical duration. Not a rate card. A band.
- Turn Our Events into this season. Dates on the six existing entries, and which parks you are running between October and June.
- Move Dimple, Aparna and Arpita in front of the corporate buyer rather than three clicks into About.
- Add the cancellation path to the process document before it becomes a CRM pipeline that does not have one.
- Draft the post-workshop impact report as a one-page template. Strongest repeat-business lever available, and it does not exist yet.
First ninety days
- Collapse seven enquiry routes into one destination. Keep the front doors and make them all land in the same place with a source attached.
- Decide what the shop is. A merchandising line that supports the brand, or a business. It currently gets the legal attention the travel side needs.
- Close or merge the second Facebook page, and find out what is on the YouTube channel before anyone plans around it.
- Give the schools line a page and a process, or stop selling it. Right now it is real revenue held together by memory.
- Reduce the jobs only Sai Kiran can do from five to two. That is the actual brief behind the automation wishlist.
Every finding in this report comes back to the same shape. The business grew past its paperwork. The Terms describe a print shop, the privacy policy describes a cake shop, the metadata describes a mindfulness studio in Hyderabad, and the process document describes a company that never has a cancellation. Meanwhile the actual business turned over ₹2.5 crore taking multinationals into national parks.
None of that is a failure of ambition or of delivery. It is what happens when the operating layer is built once at the start and the company moves on without it. The reason to do it in September rather than in January is that in September it is administration, and in January it is a problem somebody else has already found.
You asked for a set of automations across five layers. This document is what each one does, and what it takes off somebody’s desk. It is built on your own process document rather than on a generic idea of how a travel business works. The last two sections take the first phase of it and set out what gets delivered and what that costs.
What we were asked for
From the meeting, in the order you raised it.
- A website that looks slickRebuilt, capturing every enquiry into one place.
- A CRM holding every leadPipelines that match your thirty one steps rather than a generic sales funnel.
- Messaging and email journeysTriggered by the trip date, not by someone remembering.
- A site assistantTrained only on material you publish and own.
- A price generatorTrip, workshop, dates, group size.
- Signature, end to endProposals and purchase orders signed in a browser.
- Poster and caption generationFrom your inputs, inside your brand rules.
- Scheduled publishingTo the networks where you have an audience.
- An impact report to the corporate buyerNobody asked for this. We think it is the strongest repeat business lever on the list, and it is marked as ours everywhere it appears so you can strike it without argument.
- A cancellation and reschedule routeYour process document has no path for a trip that moves or a booking that falls through.
- Payment reconciliationA proforma goes out. Nothing records the money arriving.
Who this is written for
Two readers who need different things from the same document.
Every section opens in plain language and only then goes technical. There is no glossary at the back, because a term you have to go and look up has already lost you. Where a word needs explaining, it is explained beside the sentence that uses it.
Only the first phase is costed, and that is deliberate. Seventeen of the twenty seven automations form an operating spine that everything else reads from. Pricing the whole list before that spine exists would be pricing work whose shape has not settled yet. Sections 06 and 07 cover Phase 1 and nothing beyond it.
Three parts of this document are working, not described. The map of your own process, the automation list, and the message journey can all be clicked through. You will get more out of twenty minutes of clicking than out of reading this end to end.
Two things must be true before any customer messaging can be switched on. You need a registered entity with a tax number, and an enquiry phone number that is not already a personal messaging account. We could not confirm either from anything public, and your website sells physical goods without either appearing anywhere on it.
Neither is a reason to wait. Both are named beside the work that depends on them, and the rest of the build runs whatever the answer turns out to be.
Your business process flow document defines two journeys and thirty one steps. We took each one and asked a single question: does this need a person? Six do. The rest are either a message with a date on it, or a document that could write itself.
The map
Click any step to see what happens to it. The dashed items at the foot of each column are stages your document does not have.
Individuals 16 steps
Corporate 15 steps
Select a step above.
Your process document carries the same note on all three pages: if no response arrives within the expected turnaround, a follow up fires automatically. That single sentence is the most valuable thing in the document, and we could not verify whether it actually runs or whether a person does it by hand.
If it already runs, connecting to it is a smaller job than building it. Everything in this document assumes nobody is doing it, which is the more expensive of the two assumptions to be wrong about.
Twenty seven automations, each pinned to the step it replaces. Every one is separable, so any of them can be struck without unpicking the rest.
What gets built
Filter by layer. Each card carries a code, so the delivery and investment sections can point at exactly one thing rather than at a description of it.
What this means for hiring
You asked what each thing replaces. Here it is, plainly. All of it assumes the photographs and the written material keep coming from you.
- What replaces itThe content engine turns a brief into a poster and a caption inside your brand rules. Scheduled publishing puts it out on Instagram and LinkedIn.
- What still needs a personReplying to comments and messages. Judgement about what is worth posting. Sai Kiran's photographs.
- What replaces itThe design system. Colour, type, spacing and components defined once, so a new page or a new poster assembles from parts that already match.
- What still needs a personAnything genuinely new. A design system removes repetition, not creative direction.
- What replaces itThe portal requests visas, tickets and purchase orders, and chases until each one arrives.
- What still needs a personThe call when something is genuinely wrong. The portal chases; it does not reassure.
Held as optional
None of these are assumed. Each one says plainly what it costs to leave it out, which is the only honest way to present an option.
- Cancellation, reschedule and refund pathThe one journey most likely to produce an angry customer stays entirely manual, and stays invisible in the pipeline.
- Post workshop impact reportThe corporate relationship ends at the feedback form, which is the moment you hold the most evidence and give the buyer the least reason to remember you. This one is our addition, not your ask.
- Payment receipt and reconciliationMoney received stays disconnected from the deal record, so nobody can answer who has paid without opening two systems.
- Schools and campuses journeySchool enquiries keep arriving into the same intake and then get worked by hand outside any pipeline.
- Shop lifecycle automationThe shop stays a separate business that shares a logo.
- Public price configuratorPricing stays a conversation, which is slower but keeps every number under your control while the rate model settles.
- Founders' own assistantContent briefs and first drafts stay a founder's evening job.
- Vendor and property registerSupplier knowledge stays in one person's head, which is fine until that person is in a forest with no signal.
- Publishing to X and ThreadsNothing. You have no audience on either network today, so there is nothing to lose by leaving this until there is.
Two of your four lines are missing from all of this.
Schools and campuses, and the shop, appear on your website and in neither flow document. We have not assumed they are unimportant, and we have not folded them in silently either. Both are held as optional above. If they are strategic, say so and they move into the core scope. If they are not, leaving them out of the automation is the right call and costs you nothing.
You asked to see the messaging journey drawn touchpoint by touchpoint. This is a working model of it. Move through the twelve touchpoints and read what lands on the customer's phone at each one.
One customer, one trip
A four day trip to Kabini for two people. Every message below is a draft written for this document, not an approved template.
Why eleven of the twelve are the same kind of message
A design decision, and worth understanding before you sign off on any wording.
Messaging platforms sort every message into categories. A message that serves a booking someone has already made is a utility message. A message that promotes something is a promotional message. They are treated very differently, and a promotional message costs roughly seven and a half times what a utility one does.
Eleven of the twelve touchpoints above are utility. Only the last, the testimonial and next trip message, is promotional. That is deliberate. The same journey written carelessly, with one line of marketing tucked into the countdown message, reclassifies the whole sequence and multiplies what it costs to run, for no benefit to the person receiving it.
One rule shapes the opening. Replies you send inside twenty four hours of a customer writing to you are free, and that window narrows from October 2026. It is why the journey starts with questions that invite a reply rather than with a broadcast.
Business messaging requires a registered business, a tax number, and a phone number that is not already carrying a personal messaging account. Your enquiry number appears on your website footer and on a scannable code, so it is very likely already a personal account.
If it is, that number cannot be used and a new one is needed. That changes the footer, the code and anything printed. It is cheap to handle now and awkward to handle after the code is on a brochure.
Five layers, four of which you never see. And the short answer to your server question: no, you do not need one.
The whole thing on one page
Everything arrives in one place, gets worked in one place, and triggers everything else from there.
Do you need a server?
You asked directly, so here is a direct answer.
No, not for anything in the core build. Your website carries on running where it runs today. The pipeline, the messaging, the signature flow and the publishing are all subscription services that someone else keeps switched on. There is no machine for you to buy, patch or worry about. We have assumed your existing hosting stays and is adequate for the rebuilt site, which is worth measuring rather than taking on trust.
There is exactly one exception, and it is optional. The founders' own assistant, which is optional and listed as such, runs on a machine you control rather than on somebody else's. That is the entire point of it, and it is why it is the only line in this document that needs hardware.
| If you take the optional assistant | What we would put it on |
|---|---|
| Machine | A small always on virtual server, roughly 4 processors and 8 GB of memory, 100 GB of storage. Not a physical box in your office. |
| Where | An Indian region, so data stays in country and latency stays low. |
| Cost | A modest monthly hosting charge, and the only hardware cost anywhere in this document. Everything else runs on services somebody else keeps switched on. |
| What it may hold | Brand material, past captions, trip notes. Not customer passports, not visas, not signed contracts. |
| Who maintains it | Us, under support. This is not something either founder should be patching. |
One platform, or one platform with a second thing running beside it.
The customer platform you named handles contacts, deals and pipelines perfectly well at its entry level. Multi step sequences, which are the automation this whole document describes, sit on the tier above, and the step between the two is steep rather than gradual. There are two honest routes. Buy the higher tier and build every sequence once, inside one system, with one place to look when something does not fire. Or hold the platform at entry level as your record of customers and run the sequences beside it, which costs less and adds a second moving part and a seam where messages can go missing.
We would take the first unless the gap turns out to be large, and there are partner routes where a discount is normal. It is worth deciding before the build starts rather than after, because it changes where the follow up engine is built, and moving it later is rework rather than configuration. The two routes differ enough, in complexity as well as in price, that the choice deserves deciding on its own rather than by default.
Phase 1 only, and deliberately. Seventeen of the twenty seven automations, grouped into seven things that get delivered. This is the operating spine, the part that has to exist before any of the rest is worth building.
What Phase 1 delivers
Seven items. Each one is a thing you can use on the day it lands, not a milestone on a chart.
| What lands | What it means in practice |
|---|---|
| One intake, one pipelineA01 A02 A04 A05 | Enquiries stop arriving in six unconnected places. Both journeys exist as stages, so on any day you can say who is where and who has gone quiet. |
| The follow up engineA12 A13 | Nobody goes cold because a founder was in a forest with no signal. When a response deadline passes, a named person is told. |
| Structured intakeA06 A07 | The questionnaire and the behaviours conversation land as data on the record, which is what everything downstream reads from. |
| The message journeyA17 A18 A19 A20 A21 | Welcome kit, do's and don'ts, countdown, checklist and thank you go out every time rather than most times, timed off the trip date. |
| Documents and signatureA14 A15 A16 | Visas, tickets and purchase orders collected and chased without an email thread. Proposals signed in a browser. Proformas drawn from the deal. |
| Feedback captureA22 | Feedback is sent, chased once and scored against the right record, so the loop closes instead of trailing off. |
| Setup, testing and handoverNo automation code | Environments, migration of the enquiries sitting in the current six destinations, both journeys tested with real records, and a training session for each founder. |
What waits, and why
The other ten automations are not cut. They are second.
Ten automations sit after this phase: A03, A08, A09, A10, A11, A23, A24, A25, A26, A27. In order, that is the site assistant, the rate model, the price configurator, proposal generation, itinerary generation, review and testimonial routing, the impact report, the content engine, scheduled publishing and the operations dashboard. The website rebuild and the design system sit alongside them.
Each of them reads from something Phase 1 creates. A configurator needs a rate model and a record to price against. A dashboard needs a pipeline to show. Generation tools need structured intake to draw from. Built the other way round, every one of them writes into somewhere nobody owns, and a slicker website feeding the same six unconnected inboxes has not fixed anything.
Roughly five weeks from kickoff, assuming both founders are available to review as things land. It stays that short because most of this phase is configuring platforms that already exist rather than building software from nothing.
The thing most likely to move it is not us. Message templates are approved by the platform rather than by anyone in this engagement, and the entity and sender questions in section 05 have to resolve before that approval can even be requested.
One phase, seven lines, one number. Every figure is built from a task list and a role rate rather than set as a lump sum, which is why striking something from the scope moves the total in a way you can check rather than in a way you have to trust.
Phase 1, line by line
The same seven items as the previous section, in the same order, so the two pages can be read side by side. Each line names the automations it covers.
Payment schedule
Tied to delivery rather than to the calendar. Nothing falls due for something that has not landed.
What the number does not include
So that none of it arrives as a surprise later.
- Platform subscriptionsThe customer platform, the messaging provider and the signature tool are billed to you directly by them.
- Message chargesMessaging is charged per message by category. Volume drives it, so it belongs on your bill rather than in a fixed fee.
- HostingYour existing hosting continues. Phase 1 adds no server.
- A03, A08, A09, A10, A11, A23, A24, A25, A26, A27The other ten automations. Priced separately once Phase 1 is agreed, so the second number is built on what the first one actually produced rather than on what we expected it to.
- Content and photographyBoth come from you.
Each line was broken into its own task list and costed at the rate for the role doing the work, then rounded to the nearest five thousand, which is why they read as estimates rather than as quotations. Rounding moved the total by well under one percent.
Most of Phase 1 is configuration of platforms that already exist, not software written from nothing, and it is priced that way. The one genuine build is the document and purchase order portal, which is why that line sits where it does.
The total is the sum of the seven lines and nothing else. There is no management fee and no contingency line. Change what is in Phase 1 and the number moves by the lines you remove, not by a renegotiation.