# KOMTECH KOMPUTAS SERVICES
# PROCEDURE.MD — STEP-BY-STEP IMPLEMENTATION PROCEDURE

Version: 1.0
Project: Official Komtech Komputas Services Website + Service Booking + Admin CRM
Primary Stack: Laravel + MySQL + Blade + Tailwind CSS + Alpine.js/Livewire + Vite
Deployment Target: Standard PHP/MySQL hosting, with local development via XAMPP
Status Convention:
- [ ] Not started
- [~] In progress
- [x] Complete
- [!] Blocked / requires human decision

---

# 0. PURPOSE OF THIS PROCEDURE

This document is the mandatory implementation procedure for building the official Komtech Komputas Services website and business inquiry platform.

The purpose is to ensure that:

1. No major implementation phase is skipped.
2. Database, backend, frontend, admin, notifications and security are all completed.
3. Every important feature is tested before being marked complete.
4. The project can be stopped and resumed without losing context.
5. No fake business information is introduced.
6. The final application is production-ready rather than merely visually complete.

IMPORTANT:

The coding agent MUST follow this procedure in order.

The agent MUST NOT jump directly to the final website.

The agent MUST NOT mark a step complete until its completion criteria have been satisfied.

If a step cannot be completed because information or credentials are missing, mark it [!] and document the blocker in progress.md.

---

# 1. NON-NEGOTIABLE PROJECT RULES

## 1.1 Business identity

Company:

KOMTECH KOMPUTAS SERVICES

Locations:

Warri | Lagos, Nigeria

Phone:

07037304925

Email:

okomogo@gmail.com

Existing product:

Hotel Hub

Website:

https://hotelhub.com.ng

---

## 1.2 Company positioning

Komtech Komputas Services is a technology and digital solutions company helping businesses replace manual processes with practical digital systems.

Core areas:

- Business software
- POS systems
- Inventory management
- Hotel management software
- Laundry management software
- Restaurant/business management
- Custom web applications
- Progressive Web Apps
- Android applications
- Business websites
- IT support
- Computer services
- Business digitization
- AI-assisted digital solutions

Primary message:

"Technology That Works for Your Business"

Secondary concept:

"Digitize. Manage. Automate. Grow."

---

## 1.3 Never fabricate information

The application MUST NOT invent:

- Customers
- Testimonials
- Client logos
- Awards
- Revenue
- User counts
- Partnerships
- Certifications
- Years of experience
- Statistics
- Reviews
- Business achievements

Use real information only.

Internal products may be shown as Komtech products/solutions.

Conceptual projects must be clearly identified as internal, conceptual or demo material.

---

## 1.4 Development environment

Preferred:

- PHP
- Laravel
- MySQL
- Blade
- Tailwind CSS
- Alpine.js
- Livewire where useful
- Vite
- Composer
- NPM

DO NOT use Docker unless explicitly requested later.

The application must work in a normal XAMPP/MySQL environment.

---

# 2. MANDATORY PROJECT CONTROL FILES

Before implementation begins, create:

/docs/plan.md
/progress.md

Also create:

/docs/architecture.md
/docs/database.md
/docs/deployment.md
/docs/admin-guide.md

These files are part of the project and MUST be maintained.

---

# 3. PROGRESS TRACKING RULE

After every major phase:

1. Update progress.md.
2. Record:
   - Date
   - Phase
   - Work completed
   - Files changed
   - Tests performed
   - Problems encountered
   - Remaining work
   - Next step
3. Update docs/plan.md checkboxes.

The coding agent MUST read:

- docs/plan.md
- progress.md

before resuming a previously interrupted session.

---

# 4. PHASE 0 — REPOSITORY INSPECTION

## Tasks

[ ] Inspect the repository.

[ ] Determine whether it is:
- Empty
- Existing Laravel application
- Another framework
- Partially completed project

[ ] Inspect:
- composer.json
- package.json
- routes
- app/
- resources/
- database/
- config/
- public/
- existing migrations
- existing authentication
- existing components
- existing assets

[ ] Identify existing functionality.

[ ] Identify existing dependencies.

[ ] Identify potential conflicts.

[ ] Do NOT delete existing work without justification.

## Completion criteria

This phase is complete only when:

[ ] Existing project architecture is documented.

[ ] Existing useful code has been identified.

[ ] Risks and conflicts are documented.

[ ] progress.md is updated.

---

# 5. PHASE 1 — PROJECT PLAN

Create docs/plan.md.

The plan MUST contain:

[ ] Architecture

[ ] Database

[ ] Authentication

[ ] Public website

[ ] Services

[ ] Products

[ ] Portfolio

[ ] Insights/blog

[ ] Contact system

[ ] Service booking

[ ] Notifications

[ ] Appointments

[ ] Admin dashboard

[ ] Security

[ ] SEO

[ ] Testing

[ ] Deployment

Break each item into smaller tasks.

## Completion gate

Do not begin major implementation until docs/plan.md exists.

---

# 6. PHASE 2 — TECHNICAL ARCHITECTURE

Create docs/architecture.md.

Document:

[ ] Application architecture

[ ] Frontend structure

[ ] Backend structure

[ ] Database structure

[ ] Authentication

[ ] Authorization

[ ] Notification architecture

[ ] File upload architecture

[ ] Admin architecture

[ ] SEO architecture

[ ] Future extension strategy

The application should use a clean Laravel monolithic architecture.

Do not introduce microservices.

---

# 7. PHASE 3 — ENVIRONMENT SETUP

## Tasks

[ ] Confirm PHP version.

[ ] Confirm Composer.

[ ] Confirm Node/NPM.

[ ] Confirm MySQL.

[ ] Confirm Laravel.

[ ] Create/update .env.example.

Required environment variables include:

APP_NAME
APP_URL

DB_CONNECTION
DB_HOST
DB_PORT
DB_DATABASE
DB_USERNAME
DB_PASSWORD

MAIL_MAILER
MAIL_HOST
MAIL_PORT
MAIL_USERNAME
MAIL_PASSWORD
MAIL_FROM_ADDRESS
MAIL_FROM_NAME

ADMIN_NOTIFICATION_EMAIL

WHATSAPP_NUMBER

[ ] Configure local database.

[ ] Confirm application boots.

## Test

Run the appropriate Laravel development server.

Confirm the default application loads.

## Completion gate

[ ] Application starts successfully.

[ ] Database connection works.

[ ] Assets compile.

---

# 8. PHASE 4 — DATABASE DESIGN

Create docs/database.md.

Design the database before implementing forms.

Minimum tables:

[ ] users

[ ] services

[ ] service_requests

[ ] service_request_items

[ ] service_request_attachments

[ ] appointments

[ ] products

[ ] portfolio_projects

[ ] articles

[ ] contact_messages

[ ] notifications

[ ] settings

[ ] activity_logs

Optional:

[ ] industries

[ ] tags

[ ] article_tags

---

# 9. PHASE 5 — DATABASE MIGRATIONS

Create migrations.

## Required relationships

Users:
- Admin users.

Services:
- Can be selected by service requests.

Service requests:
- Customer/project information.
- Status.
- Contact preference.
- Notes.
- Reference number.

Service request items:
- Allows multiple selected services.

Attachments:
- Belong to service requests.

Appointments:
- Connected to service requests.

Products:
- Komtech products.

Portfolio:
- Projects.

Articles:
- Blog/insight content.

Contact messages:
- General inquiries.

Settings:
- Configurable company information.

Activity logs:
- Important admin actions.

## Completion gate

[ ] All migrations created.

[ ] Foreign keys checked.

[ ] Indexes added where useful.

[ ] Reference number uniqueness enforced.

[ ] Migrations run successfully on a clean database.

---

# 10. PHASE 6 — MODELS AND RELATIONSHIPS

Create Laravel models.

At minimum:

[ ] User

[ ] Service

[ ] ServiceRequest

[ ] ServiceRequestItem

[ ] ServiceRequestAttachment

[ ] Appointment

[ ] Product

[ ] PortfolioProject

[ ] Article

[ ] ContactMessage

[ ] Notification

[ ] Setting

[ ] ActivityLog

Define relationships.

Use appropriate casts.

Protect against mass assignment.

## Completion gate

[ ] Models load.

[ ] Relationships work.

[ ] Basic model tests pass.

---

# 11. PHASE 7 — SEED DATA

Create seeders for real Komtech information.

Services:

1. Website Development
2. POS & Inventory
3. Hotel Software
4. Laundry Software
5. Android/PWA Applications
6. IT Support
7. Business Digitization
8. Custom Software

Products:

1. SmartShop
2. Hotel Hub
3. Laundry Management Solution

Hotel Hub external URL:

https://hotelhub.com.ng

DO NOT seed fake customers.

DO NOT seed fake testimonials.

DO NOT seed fake inquiries.

## Completion gate

[ ] Fresh database can be seeded.

[ ] Seed data is accurate.

[ ] No fabricated claims are included.

---

# 12. PHASE 8 — AUTHENTICATION

Implement secure admin authentication.

Requirements:

[ ] Login

[ ] Logout

[ ] Password hashing

[ ] Password reset architecture

[ ] Session protection

[ ] CSRF

[ ] Rate limiting

[ ] Admin authorization

[ ] Protected admin routes

Do NOT hardcode production credentials.

Provide secure setup instructions.

## Test

[ ] Admin can log in.

[ ] Incorrect password fails.

[ ] Unauthenticated user cannot access admin.

[ ] Logout works.

---

# 13. PHASE 9 — PUBLIC DESIGN SYSTEM

Before building every page, establish a consistent design system.

Define:

[ ] Typography

[ ] Colors

[ ] Spacing

[ ] Buttons

[ ] Cards

[ ] Forms

[ ] Navigation

[ ] Footer

[ ] Alerts

[ ] Badges

[ ] Modals

[ ] Loading states

[ ] Empty states

[ ] Error states

The design should feel like a professional technology company.

Avoid generic template appearance.

---

# 14. PHASE 10 — GLOBAL NAVIGATION

Create desktop navigation:

Home
Services
Solutions
Portfolio
About
Insights
Contact
Book a Service

Mobile navigation must be fully responsive.

Primary mobile CTA:

Book a Service

Add a floating WhatsApp button.

---

# 15. PHASE 11 — HOMEPAGE

Build the homepage in this order:

[ ] Hero

[ ] Value proposition

[ ] Services

[ ] Products/solutions

[ ] Business problem section

[ ] How Komtech works

[ ] Portfolio

[ ] Industries

[ ] Why Komtech

[ ] Insights

[ ] Final CTA

[ ] Footer

Hero:

"Technology That Works for Your Business"

Supporting copy:

"Komtech Komputas Services builds practical digital solutions that help businesses manage operations, serve customers, reduce manual work and grow with confidence."

Primary CTA:

BOOK A SERVICE

Secondary CTA:

EXPLORE OUR SOLUTIONS

## Completion gate

[ ] Desktop checked.

[ ] Mobile checked.

[ ] Buttons work.

[ ] No placeholder copy.

---

# 16. PHASE 12 — ABOUT PAGE

Build /about.

Include:

[ ] Company introduction

[ ] Technology philosophy

[ ] Business-focused approach

[ ] Areas of expertise

[ ] Practical development approach

[ ] Support philosophy

Do not make the founder the entire focus.

## Completion gate

[ ] Accurate.

[ ] No fabricated claims.

[ ] Responsive.

---

# 17. PHASE 13 — SERVICES SYSTEM

Build:

/services

/services/{slug}

Services:

[ ] Website Development

[ ] POS & Inventory

[ ] Hotel Software

[ ] Laundry Software

[ ] Android/PWA Applications

[ ] IT Support

[ ] Business Digitization

[ ] Custom Software

Each service page must include:

[ ] Title

[ ] Description

[ ] Benefits

[ ] Use cases

[ ] Relevant industries

[ ] CTA

[ ] Book This Service

---

# 18. PHASE 14 — PRODUCTS / SOLUTIONS

Build:

/solutions

/solutions/{slug}

## SmartShop

Show:

[ ] POS

[ ] Sales

[ ] Products

[ ] Inventory

[ ] Customers

[ ] Reports

[ ] Business management

## Hotel Hub

Show:

[ ] Hotel management

[ ] Booking

[ ] Rooms

[ ] Guests

[ ] Operations

[ ] Outlets

[ ] POS

External URL:

https://hotelhub.com.ng

## Laundry Management

Show:

[ ] Customer management

[ ] Customer lookup

[ ] Laundry orders

[ ] Services

[ ] Washing

[ ] Urgent washing

[ ] Ironing

[ ] Payments

[ ] Invoices

[ ] Branch management

[ ] Reporting

[ ] Multi-branch architecture

[ ] Arabic-ready interface

---

# 19. PHASE 15 — PORTFOLIO

Build:

/portfolio

/portfolio/{slug}

Initial entries:

[ ] SmartShop

[ ] Hotel Hub

[ ] Laundry Management Solution

[ ] Hotel Management Software

[ ] Custom Business Software

If screenshots are unavailable:

Use professional product mockups.

Do NOT present fictional clients.

---

# 20. PHASE 16 — INDUSTRIES

Create an Industries section.

Include:

[ ] Retail

[ ] Hospitality

[ ] Laundry

[ ] Restaurants

[ ] Schools

[ ] Logistics

[ ] Professional Services

[ ] SMEs

Explain relevant solutions for each.

---

# 21. PHASE 17 — CONTACT PAGE

Build /contact.

Display:

Komtech Komputas Services

Warri | Lagos, Nigeria

07037304925

okomogo@gmail.com

Include:

[ ] Contact form

[ ] Phone CTA

[ ] WhatsApp CTA

[ ] Email CTA

[ ] Book Service CTA

---

# 22. PHASE 18 — CONTACT FORM

Fields:

[ ] Name

[ ] Email

[ ] Phone

[ ] Subject

[ ] Message

Requirements:

[ ] Client validation

[ ] Server validation

[ ] Database storage

[ ] Admin notification

[ ] Success message

[ ] Spam protection

## Completion gate

Submit a real test message.

Confirm:

[ ] Database record exists.

[ ] Admin notification works.

[ ] Success page works.

---

# 23. PHASE 19 — SERVICE BOOKING WIZARD

This is a CORE FEATURE.

Route:

/book-service

Create a multi-step wizard.

---

## STEP 1 — SERVICE

Options:

[ ] Website

[ ] POS

[ ] Inventory System

[ ] Hotel Software

[ ] Laundry Software

[ ] Android App

[ ] PWA/Web App

[ ] Custom Software

[ ] IT Support

[ ] Computer Services

[ ] Business Digitization

[ ] Consultation

[ ] Other

Allow multiple services when appropriate.

---

## STEP 2 — BUSINESS INFORMATION

Fields:

[ ] Full Name

[ ] Company Name

[ ] Email

[ ] Phone

[ ] Business Location

[ ] Business Type

Business types:

Retail
Hotel
Laundry
Restaurant
School
Logistics
Manufacturing
Professional Services
Other

---

## STEP 3 — PROJECT DETAILS

Fields:

[ ] Project title

[ ] Project description

[ ] Current process

[ ] Main problem

[ ] Desired solution

[ ] Number of users

[ ] Number of branches

[ ] Existing software

[ ] Budget range

[ ] Preferred start date

[ ] Optional attachment

---

## STEP 4 — CONTACT PREFERENCE

Options:

[ ] Phone

[ ] WhatsApp

[ ] Email

[ ] Online Meeting

Allow preferred date/time.

---

## STEP 5 — REVIEW

Display all information.

Allow user to go back and edit.

Button:

SUBMIT REQUEST

---

# 24. PHASE 20 — REQUEST PROCESSING

On submission:

[ ] Validate all data.

[ ] Validate uploaded files.

[ ] Sanitize data.

[ ] Store request.

[ ] Store selected services.

[ ] Store attachments.

[ ] Generate unique reference.

Format:

KKS-2026-000001

Reference number must be unique.

[ ] Create notification.

[ ] Send admin email.

[ ] Send customer confirmation.

[ ] Show success page.

---

# 25. PHASE 21 — FILE UPLOAD SECURITY

If attachments are enabled:

Allow only:

PDF
DOC
DOCX
JPG
JPEG
PNG

Requirements:

[ ] MIME validation

[ ] File size limit

[ ] Secure filename

[ ] Storage outside executable public paths where appropriate

[ ] Authorization before download

[ ] No executable uploads

Test malicious extensions.

---

# 26. PHASE 22 — EMAIL SYSTEM

Create mail/notification classes.

Required notifications:

[ ] AdminNewRequest

[ ] CustomerRequestConfirmation

[ ] AppointmentScheduled

[ ] StatusChanged

Admin notification must include:

[ ] Reference number

[ ] Customer

[ ] Company

[ ] Service

[ ] Project description

[ ] Budget

[ ] Contact preference

[ ] Preferred date

[ ] Submission time

Add:

VIEW REQUEST

button.

---

# 27. PHASE 23 — ADMIN DASHBOARD

Route:

/admin

Dashboard cards:

[ ] Total requests

[ ] New requests

[ ] Consultations

[ ] Quoted projects

[ ] Active projects

[ ] Completed projects

[ ] Monthly requests

Charts:

[ ] Requests by month

[ ] Requests by service

[ ] Requests by status

---

# 28. PHASE 24 — ADMIN REQUEST MANAGEMENT

Route:

/admin/inquiries

Implement:

[ ] Search

[ ] Filter

[ ] Sort

[ ] Pagination

[ ] View

[ ] Status change

[ ] Notes

[ ] Attachments

[ ] Appointment scheduling

[ ] Archive

Statuses:

NEW
CONTACTED
CONSULTATION_SCHEDULED
QUOTED
IN_PROGRESS
COMPLETED
CANCELLED

Test every status transition.

---

# 29. PHASE 25 — APPOINTMENTS

Build appointment management.

Fields:

[ ] Customer

[ ] Service request

[ ] Date

[ ] Time

[ ] Meeting type

[ ] Notes

[ ] Status

Meeting types:

Phone
WhatsApp
Google Meet
Zoom
Physical Meeting

Do not pretend that Google Meet/Zoom integration exists unless actually implemented.

---

# 30. PHASE 26 — ADMIN SERVICES

Admin must be able to:

[ ] Create service

[ ] Edit service

[ ] Deactivate service

[ ] Reorder service

[ ] Feature service

[ ] Edit icon

[ ] Edit description

[ ] Edit slug

[ ] Edit CTA

---

# 31. PHASE 27 — ADMIN PRODUCTS

Admin must be able to:

[ ] Create product

[ ] Edit product

[ ] Delete/deactivate product

[ ] Edit features

[ ] Edit external URL

[ ] Upload image

[ ] Feature product

---

# 32. PHASE 28 — ADMIN PORTFOLIO

Admin must be able to:

[ ] Create project

[ ] Edit project

[ ] Publish/unpublish

[ ] Add images

[ ] Set industry

[ ] Add challenge

[ ] Add solution

[ ] Add features

[ ] Add technology information

[ ] Add external URL

[ ] Feature project

---

# 33. PHASE 29 — BLOG / INSIGHTS

Build:

/insights

/insights/{slug}

Admin:

[ ] Create article

[ ] Edit article

[ ] Publish

[ ] Unpublish

[ ] Add featured image

[ ] Add category

[ ] Add SEO title

[ ] Add SEO description

Articles should cover topics such as:

- Business technology
- POS
- Inventory
- Hotel technology
- Laundry technology
- Digital transformation
- AI for business
- SME software
- IT tips

---

# 34. PHASE 30 — ADMIN SETTINGS

Create settings for:

[ ] Company name

[ ] Phone

[ ] Email

[ ] WhatsApp

[ ] Locations

[ ] Social links

[ ] Logo

[ ] Favicon

[ ] SEO title

[ ] SEO description

[ ] Notification email

[ ] WhatsApp number

Do not hardcode configurable values throughout the application.

---

# 35. PHASE 31 — WHATSAPP

Implement floating WhatsApp button.

Number:

07037304925

Message:

"Hello Komtech Komputas, I would like to enquire about your services."

Make number configurable through settings.

---

# 36. PHASE 32 — SEO

Implement:

[ ] Page titles

[ ] Meta descriptions

[ ] Canonical URLs

[ ] OpenGraph

[ ] Social cards

[ ] Sitemap

[ ] Robots.txt

[ ] Organization schema

[ ] Service schema where appropriate

[ ] Article schema

[ ] WebSite schema

Target relevant searches naturally, including:

- software company Nigeria
- business software Nigeria
- POS software Nigeria
- inventory software Nigeria
- hotel management software Nigeria
- laundry management software
- custom software development Nigeria
- website development Nigeria
- Android app development Nigeria
- IT support Nigeria

Do not keyword stuff.

---

# 37. PHASE 33 — PERFORMANCE

Check:

[ ] Image sizes

[ ] Lazy loading

[ ] CSS bundle

[ ] JavaScript bundle

[ ] Database queries

[ ] N+1 queries

[ ] Caching where appropriate

[ ] Unused libraries

[ ] Page loading speed

---

# 38. PHASE 34 — ACCESSIBILITY

Check:

[ ] Semantic HTML

[ ] Labels

[ ] Keyboard navigation

[ ] Focus states

[ ] Contrast

[ ] Alt text

[ ] Screen-reader-friendly controls

[ ] Mobile touch targets

---

# 39. PHASE 35 — SECURITY HARDENING

Verify:

[ ] CSRF

[ ] XSS protection

[ ] SQL injection protection

[ ] Authorization

[ ] Validation

[ ] Rate limiting

[ ] Secure uploads

[ ] Secure sessions

[ ] Password hashing

[ ] Protected admin routes

[ ] No sensitive credentials in source code

[ ] No debug mode in production

[ ] Proper error handling

---

# 40. PHASE 36 — ERROR PAGES

Create polished:

[ ] 404

[ ] 403

[ ] 419

[ ] 429

[ ] 500

Production errors must not expose stack traces.

---

# 41. PHASE 37 — ACTIVITY LOGGING

Record important admin actions:

[ ] Login

[ ] Inquiry updates

[ ] Status changes

[ ] Service changes

[ ] Product changes

[ ] Portfolio changes

[ ] Article publication

[ ] Settings changes

Include:

- User
- Action
- Entity
- Timestamp
- Relevant metadata

---

# 42. PHASE 38 — MOBILE QA

Test at minimum:

[ ] Small Android phone

[ ] Large Android phone

[ ] iPhone-sized viewport

[ ] Tablet

[ ] Desktop

Check:

[ ] Navigation

[ ] Hero

[ ] Forms

[ ] Buttons

[ ] Tables

[ ] Dashboard

[ ] Cards

[ ] Images

[ ] No horizontal overflow

---

# 43. PHASE 39 — FUNCTIONAL TESTING

Test public website:

[ ] Homepage

[ ] About

[ ] Services

[ ] Service detail

[ ] Solutions

[ ] Product detail

[ ] Portfolio

[ ] Portfolio detail

[ ] Insights

[ ] Article

[ ] Contact

[ ] Booking

[ ] Privacy

[ ] Terms

---

# 44. PHASE 40 — BOOKING SYSTEM TEST

Perform a complete real test.

Scenario:

A visitor wants laundry software.

Steps:

[ ] Select Laundry Software.

[ ] Enter customer details.

[ ] Enter business details.

[ ] Describe requirement.

[ ] Select contact preference.

[ ] Submit.

Verify:

[ ] Validation works.

[ ] Request saved.

[ ] Reference generated.

[ ] Admin notification sent.

[ ] Customer confirmation sent.

[ ] Request appears in admin.

[ ] Status can be changed.

[ ] Notes can be added.

[ ] Appointment can be scheduled.

This test MUST pass before the booking system is marked complete.

---

# 45. PHASE 41 — CONTACT TEST

Submit a contact request.

Verify:

[ ] Validation

[ ] Database

[ ] Notification

[ ] Success message

[ ] Admin visibility

---

# 46. PHASE 42 — ADMIN SECURITY TEST

Test:

[ ] Direct access without login

[ ] Invalid login

[ ] Logout

[ ] Session expiration

[ ] Unauthorized access

[ ] Protected attachment access

---

# 47. PHASE 43 — DATABASE CLEAN INSTALL TEST

This is mandatory.

Create a clean test database.

Run:

[ ] Migrations

[ ] Seeders

[ ] Application setup

Confirm no migration or seeding errors.

The application must be reproducible from a clean database.

---

# 48. PHASE 44 — BUILD TEST

Run the production asset build.

Confirm:

[ ] No build errors

[ ] No critical warnings

[ ] CSS builds

[ ] JavaScript builds

[ ] Vite assets load correctly

---

# 49. PHASE 45 — LARAVEL TESTS

Run:

php artisan test

Fix all failures.

Do not ignore failing tests.

Document remaining known issues if a test cannot reasonably be fixed.

---

# 50. PHASE 46 — LINK AUDIT

Check every internal link.

Check:

[ ] Navigation

[ ] Buttons

[ ] Service links

[ ] Product links

[ ] Portfolio links

[ ] Article links

[ ] Contact links

[ ] Book Service links

[ ] Admin links

[ ] External Hotel Hub link

No broken links.

---

# 51. PHASE 47 — CONTENT AUDIT

Search project files for:

Lorem ipsum

Your Company

John Doe

Example

Test

Placeholder

Coming Soon

TODO

Fake testimonial

Fake client

Remove unintended placeholders.

---

# 52. PHASE 48 — ENVIRONMENT / PRODUCTION CHECK

Before deployment:

[ ] APP_ENV configured correctly.

[ ] APP_DEBUG=false in production.

[ ] APP_KEY exists.

[ ] Database credentials configured.

[ ] Mail credentials configured.

[ ] Notification email configured.

[ ] Storage configured.

[ ] File permissions checked.

[ ] Cache configuration checked.

[ ] Queue configuration documented if enabled.

---

# 53. PHASE 49 — DOCUMENTATION

Complete:

README.md

docs/architecture.md

docs/database.md

docs/deployment.md

docs/admin-guide.md

docs/plan.md

progress.md

README must explain:

[ ] Requirements

[ ] Installation

[ ] Database setup

[ ] Environment variables

[ ] Local development

[ ] Asset building

[ ] Admin creation

[ ] Migrations

[ ] Seeders

[ ] Email configuration

[ ] Production deployment

---

# 54. PHASE 50 — FINAL VISUAL REVIEW

Do a complete visual review.

Check:

[ ] Typography

[ ] Spacing

[ ] Buttons

[ ] Cards

[ ] Navigation

[ ] Footer

[ ] Forms

[ ] Dashboard

[ ] Empty states

[ ] Loading states

[ ] Error states

[ ] Success states

[ ] Mobile layout

[ ] Desktop layout

The final product must look professionally designed.

---

# 55. PHASE 51 — FINAL BUSINESS REVIEW

Confirm that a new visitor can understand within a short time:

1. Who Komtech is.
2. What Komtech does.
3. What services are available.
4. What products exist.
5. Who the services are for.
6. How to contact Komtech.
7. How to request a service.

The main conversion path must be obvious:

VISITOR
↓
SERVICE
↓
BOOK A SERVICE
↓
PROJECT DETAILS
↓
SUBMIT
↓
REFERENCE NUMBER
↓
ADMIN NOTIFICATION
↓
ADMIN FOLLOW-UP

---

# 56. PHASE 52 — FINAL ACCEPTANCE TEST

The project can ONLY be declared complete when all of the following are true:

[ ] Public website works.

[ ] Mobile website works.

[ ] Admin authentication works.

[ ] Admin dashboard works.

[ ] Services work.

[ ] Products work.

[ ] Portfolio works.

[ ] Insights work.

[ ] Contact system works.

[ ] Service booking works.

[ ] Database works.

[ ] Reference numbers work.

[ ] Admin notifications work.

[ ] Customer confirmation works.

[ ] Appointment system works.

[ ] Admin status management works.

[ ] File upload security works.

[ ] SEO implemented.

[ ] Security checked.

[ ] Tests pass.

[ ] Production build passes.

[ ] Documentation completed.

[ ] No unintended placeholders.

[ ] No fake business claims.

[ ] progress.md updated.

[ ] docs/plan.md updated.

---

# 57. FINAL REPORT

When everything is complete, provide a final report containing:

## Project Status

Complete / Incomplete

## Features Built

List every major feature.

## Database

List tables created.

## Admin

List admin functionality.

## Notifications

Explain email notification setup.

## Testing

List tests performed and results.

## Deployment

Provide exact deployment instructions.

## Configuration Still Required

List things requiring real credentials or human action.

## Known Limitations

List anything intentionally deferred.

---

# 58. FUTURE FEATURES — DO NOT BUILD UNLESS REQUESTED

The architecture should allow these later:

- Customer accounts
- Customer portal
- Online payments
- Quotes
- Invoices
- Support tickets
- Maintenance subscriptions
- Project tracking
- Automated WhatsApp notifications
- WhatsApp API
- Online payments
- Google Meet integration
- Zoom integration
- CRM expansion
- Customer communication history
- Software demos
- Subscription plans

Do NOT add unnecessary complexity to version 1.

---

# 59. RESUME PROCEDURE

If development stops for any reason:

1. Read docs/plan.md.
2. Read progress.md.
3. Inspect current git/project state.
4. Identify the last completed phase.
5. Identify incomplete tasks.
6. Continue from the first incomplete task.
7. Do not redo completed work unnecessarily.
8. Run relevant tests before continuing.

---

# 60. AGENT BEHAVIOUR

The coding agent must:

- Think before coding.
- Inspect before changing.
- Plan before implementing.
- Test before declaring completion.
- Fix errors instead of ignoring them.
- Document important decisions.
- Avoid fabricated content.
- Avoid unnecessary dependencies.
- Avoid destructive operations.
- Keep progress.md updated.
- Keep docs/plan.md updated.

The coding agent must NOT:

- Skip database design.
- Skip authentication.
- Skip validation.
- Skip notifications.
- Skip admin functionality.
- Skip testing.
- Skip security.
- Declare completion based only on visual appearance.

---

# 61. FINAL COMMAND

START NOW.

First:

1. Inspect the repository.
2. Create docs/plan.md.
3. Create progress.md.
4. Create docs/architecture.md.
5. Create docs/database.md.
6. Report the repository findings.
7. Begin PHASE 1 only after documenting the current state.

Proceed sequentially.

Do not skip phases.

Do not silently mark incomplete work as complete.

At the end of every major phase, update progress.md.

The objective is not simply to build a website.

The objective is to build the professional digital home and customer acquisition system for:

# KOMTECH KOMPUTAS SERVICES

The finished platform should communicate:

# TECHNOLOGY THAT WORKS FOR YOUR BUSINESS

and provide a reliable path from:

# DISCOVERY → SERVICE REQUEST → NOTIFICATION → ADMIN FOLLOW-UP → CUSTOMER