EidenTech brings custom website development and AI chatbot development into one project when the two experiences need to work together. Visitors can research your services in clear, searchable pages, ask a company-specific question, and choose a form or conversation to contact you. The first release is planned around that complete journey.
One connected website and chatbot, with clear responsibilities
This combined service is for businesses that need both a new website and an assistant working from the same approved offer. It has a different scope from adding a widget to an existing site.
- Shared approved company knowledge
- Searchable website + optional assistant
- Validated form or chat enquiry
- One sales follow-up workflow
A new company website with lead capture
Plan service content, a contact form, and company-specific conversations together. The team receives an agreed lead record instead of separate, disconnected enquiry paths.
A service website with repeated questions
Publish common answers in the pages and let the assistant clarify individual project needs. Both experiences use the same approved service information.
A website rebuild with CRM handoff
Review important existing URLs and sales workflows. Include redirect planning, validated forms, chat qualification, and the integration target in one release brief.
A staged launch
Release a complete website and enquiry flow first when content is the main priority. Add or expand the assistant once the approved knowledge, lead fields, and ownership are ready.
How we approach your project
Share one approved source of company information
Start with your services, audience, delivery process, real project evidence, and the questions prospects ask. This becomes the basis for the page plan and the assistant’s approved answers. A page should still explain the service fully without requiring a conversation. The chatbot can clarify requirements and suggest the relevant next step, while pricing, contractual commitments, and unsupported claims stay with the team. We agree how a change to the offer reaches both the website and the assistant.
Design discovery and conversation together
Searchable service pages, visible questions and answers, understandable navigation, and mobile layouts help a visitor decide whether to enquire. The assistant appears as an optional continuation of that experience. We plan where it should offer help, which project context it can carry forward, and how it asks for contact information. Visitors who prefer a form keep a direct route to the team. Keyboard access, readable contrast, reserved widget space, and reduced-motion behaviour are considered across both paths.
Connect both enquiry paths to the same workflow
Define the minimum information needed for follow-up, the storage destination, and who owns each enquiry. The website form and chatbot use server-side validation rather than trusting browser input or model-generated fields. Google Sheets is one supported destination; a CRM connection is scoped against its API and permissions. We review create versus update behaviour, duplicate submissions, unavailable integrations, and the acknowledgement shown to a visitor. Provider credentials belong on the server, and the application only confirms a saved enquiry after storage succeeds.
Release with clear checks and ongoing ownership
Agree acceptance criteria for page content, search foundations, device layouts, conversations, lead storage, and error handling. Test the website with the assistant closed as well as open. Account for hosting, model usage, content updates, and maintenance in the handover so the operating responsibilities are visible. After launch, review actual enquiries and the questions visitors ask. These observations inform improvements; a combined website and chatbot does not establish a guaranteed conversion uplift or search position.
What we can deliver
We agree the requirements and responsibilities before development begins. Your project scope can include:
- A shared page and conversation brief with approved business information and a first-release scope.
- Responsive service pages, search foundations, accessible navigation, and a clear contact journey.
- A company-scoped chat widget, server-side model integration, validated contact capture, and a supported lead destination.
- Website and conversation acceptance checks, deployment planning, account ownership, and maintenance handover.
Choose the right starting scope
Compare what the release must accomplish, the integrations it needs, and who will operate it. These are planning options, rather than fixed packages or price quotes.
What affects development and operating cost?
A useful quote separates the initial build, recurring services, assumptions, and exclusions. Bring these four decisions to the first conversation.
- Website scope
- Distinct pages, content preparation, responsive design, publishing needs, and existing URL migration.
- Assistant scope
- Approved knowledge, conversation goals, required contact fields, document retrieval if needed, and supported actions.
- Shared sales workflow
- Storage destination, field mapping, duplicate handling, follow-up ownership, and failure recovery for both enquiry paths.
- Launch and operation
- Acceptance checks, account handover, hosting, model usage, monitoring, content changes, and ongoing maintenance.
Acceptance checks for your first release
Use observable checks to assess the implementation and handover. The final test plan follows the agreed scope and the systems your business uses.
- Service pages and chatbot answers describe the same approved offer and do not invent commitments.
- A visitor can research the services and contact the team without opening chat.
- Forms and conversations enforce the agreed minimum contact requirements on the server.
- Both enquiry paths reach the agreed lead destination with enough context for follow-up.
- Mobile, keyboard, unavailable-provider, and failed-save behaviour are included in release checks.
- The handover identifies who owns content, hosting, AI providers, integrations, and ongoing evaluation.
Technology choices for your requirements
The stack follows your integrations, operating model, and maintenance needs. These are options to review during discovery, rather than a fixed stack promised for every project.
- Next.js, React and TypeScript website and chat components
- Server-side form, generation and lead-validation APIs
- Supported AI model APIs and Google Sheets or CRM connections
Explore the assistant on this website
Our company assistant demonstrates approved business answers, progressive project questions, and a Google Sheets lead handoff. The application requires a name and valid email or phone before it saves an enquiry.
Read the implementation story for the flow, validation, failure handling, and current limitations. Opening the assistant stages a project question; it does not send a message or save a lead.
Plan your chatbot’s job in three decisions
Choose the conversation goal, approved information, and handoff. This planner creates a starting brief you can copy and discuss with us. It works in your browser without collecting contact details.
Planning questions, answered
Can you build an AI chatbot and a custom website in one project?
Yes. We can plan the company pages, approved assistant answers, enquiry flow, and lead destination together. The proposal separates the website, chatbot, integration, and ongoing operating responsibilities so you can assess each part.
Can you add the chatbot to my existing website instead?
Yes. We can review your current website, integration options, content, and enquiry process, then scope the chatbot as a separate addition. A full rebuild is only proposed when the website itself needs to change.
Will the chatbot replace our website forms?
It does not need to. A form and chat can remain available together, with consistent validation and a shared follow-up workflow. Visitors should be able to choose the contact method that suits them.
What affects the cost of the combined project?
The page count, content responsibilities, design scope, chatbot knowledge, supported actions, integrations, and launch checks all affect development effort. Hosting, model usage, and maintenance are considered separately from the initial build. We prepare a project-specific proposal after reviewing the brief.
Who owns the website and AI provider accounts?
We agree source-code access, domain and hosting ownership, provider accounts, integration credentials, and content update responsibilities before delivery. The handover should make it clear how you can operate and maintain each part of the system.
Practical guides for this decision
Website vs chatbot: what helps generate business leads?
A website explains your offer; a chatbot can help visitors discuss it. Plan both around useful information, qualified contact capture, and a clear follow-up.
Read the planning guide ↗WEBSITE PLANNINGHow to plan a website for your company
A practical brief for a company website: define the audience, decide what to publish, and plan the enquiry journey before choosing features.
Read the planning guide ↗CHATBOT PLANNINGHow much does an AI chatbot cost for a business?
A practical way to assess chatbot development and operating costs without treating a generic price range as a project quote.
Read the planning guide ↗Chatbot integrationChatbot CRM Integration: From Conversation to a Useful Lead
Plan the fields, validation, permissions and failure recovery that turn a chatbot conversation into a record your sales team can act on.
Read the planning guide ↗Tell us what needs to work better.
Share your idea, existing workflow, and the outcome you need. We will help shape a practical starting point.
Start a project conversation ↗Read our website, chatbot, and product planning guides →