1. Lead Submission

The process begins when a potential client submits their requirements through our contact form.

Once we receive the inquiry, we review the information provided and contact the lead.

Our primary communication is usually through email, although we may also contact the client through WhatsApp when appropriate.

At this stage, we determine which communication method is most convenient for the client.

2. Choosing the Communication Method

Not every client prefers to communicate in the same way.

Some clients prefer to have a direct conversation through a meeting, while others prefer to handle the entire process through email.

We accommodate both.

Meeting-Based Clients

If the client prefers a meeting, we schedule a meeting through Calendly.

We offer a 30-minute free consultation where we discuss their requirements, understand their situation, and determine how we may be able to help.

Email-Based Clients

Some clients do not need or want a Zoom or Google Meet meeting.

They prefer to communicate entirely through email.

For these clients, the complete process can be handled digitally through email, including:

• Requirement discussions
• Questions and answers
• Project clarification
• Proposal/quotation
• Agreement
• Signing
• Payment
• Project updates
• Other necessary communication

This means a client does not have to attend a meeting simply to work with us.

If they are comfortable handling everything digitally through email, we allow them to do so.

3. Free Consultation

For clients who prefer a meeting, we provide a 30-minute free consultation.

The purpose of this consultation is to understand:

• What the client needs
• What problem they are trying to solve
• What they want to build or improve
• Their expectations
• Their preferred approach
• The potential scope of the project

The consultation is also an opportunity for the client to ask questions and understand how we work.

There is no requirement for the client to proceed after the consultation.

4. Client Decision After Consultation

After the consultation, the client decides whether they are interested in moving forward.

If the client is satisfied with the discussion and wants to proceed, they may request a quotation.

In many cases, the next step is a formal quotation based on the requirements discussed.

If the client decides that our service is not the right fit for them, the process does not move forward.

We maintain a professional relationship with the client and leave the door open for future opportunities.

There is no pressure to proceed.

5. Quotation & Transparent Budget

When the client requests a quotation, we prepare a quotation based on the discussed requirements and expected scope.

The budget is kept transparent.

The client can see what the proposed work involves and how the pricing relates to the required work.

The purpose is to make it easy for the client to understand:

What needs to be done → How the work will be approached → What it will cost → What the expected timeline is

This gives the client enough information to make an informed decision.

6. Quotation Review & Negotiation

The client reviews the quotation.

If they are satisfied with the quotation, the process can move forward.

If they have concerns about the budget, scope, timeline, or specific requirements, they can communicate those concerns.

If the client wants another discussion about the quotation, we can arrange another meeting.

During this discussion, the client can explain:

• Which parts they like
• Which parts they do not prefer
• Where they need flexibility
• Which requirements are most important
• Where they may need to compromise
• What changes they would like to make to the proposed scope

We then work toward a mutually acceptable decision.

The goal is not simply to push a fixed quotation.

The goal is to reach a clear understanding between both parties regarding scope, budget, timeline, and expectations.

7. Agreement, Signing & Payment

Once both parties agree on the project scope and commercial terms, the project moves forward through the required digital process.

The client can complete the necessary:

• Agreement
• Signing
• Payment
• Other project formalities

These processes can be completed digitally.

For clients who prefer email-based communication, they do not need to attend a separate meeting to complete these steps.

8. Client Portal & Project Visibility

Once the client becomes an active client, they have access to the client portal.

The client portal provides a centralized place for project-related updates and information.

This gives the client visibility into the project without requiring them to constantly ask:

"What is happening with my project?"

The client can receive updates through the portal and remain informed about the progress of the work.

This is particularly useful for clients who prefer a fully digital workflow.

9. Determining the Project's Existing Technical Situation

Once the project officially begins, we determine what technical access is available.

There are two primary situations.

Situation A — Client Has No Existing Access

The client may have no existing website, hosting, server, or development access.

In this case, we establish the necessary development environment.

Situation B — Client Already Has Existing Access

The client may already have a domain, hosting, server, website, CMS, database, or other infrastructure.

In this case, we work with the client's existing environment.

The process is different depending on which situation applies.

10. Client-Owned Domain, Hosting & Infrastructure

For important infrastructure such as domains, hosting, and servers, our preferred approach is to keep everything under the client's own account.

Whenever possible, the client purchases these services using:

Their own email → Their own account → Their own payment method/card

This means we do not need to own the domain or hosting account ourselves.

The client remains the actual account holder and owner.

We simply receive the access required to perform the work.

This is important because the client should always retain control over their most important digital assets.

11. Access During Active Development

While we are actively working on the project, we may have the required access to the client's systems.

This access can remain active for as long as the development work requires it.

For example, if a project takes six months, the necessary access may remain available throughout those six months.

The duration of the project does not change the ownership structure.

The client owns the accounts.

We have authorized access to perform the work.

12. Existing Website: Temporary Access & Assessment

If the client already has a website and comes to us with an issue or a requirement, we may request temporary or appropriate access to the relevant systems.

We use this access to inspect the existing setup and understand the actual situation.

We determine:

• What the problem is
• What is causing the problem
• What needs to be changed
• What technical work is required
• How complex the solution is
• What timeline may be required

The purpose of the access is to properly understand the problem before proposing a solution.

13. Solution & Quotation for Existing Problems

After assessing the existing system, we explain the recommended solution.

If the work requires a separate scope or additional budget, we provide a quotation.

The client can understand:

The problem → The solution → The required work → The estimated timeline → The cost

This ensures that the client is not asked to approve work without understanding what they are paying for.

14. Development Environment & Live Preview

For clients who do not have existing access to a development environment, we provide a live development/preview environment.

The client receives a live URL where they can see the project while development is taking place.

They do not have to wait until the entire project is completed.

As work progresses, the live preview is updated regularly.

This allows the client to see:

• What has been completed
• What is currently being developed
• How the design is progressing
• How different sections are taking shape
• What still needs improvement

This creates transparency throughout the development process.

15. Why Full Access Is Not Provided During Development

During active development, the client may not receive full administrative, server, or production-level access immediately.

This is because the project is still under development and has not yet reached the final deployment and handover stage.

Providing full production-level access before it is required does not necessarily provide any benefit to the client and can introduce unnecessary risks or conflicts while development is still taking place.

Instead, the client has visibility through the live preview environment.

They can see the actual work without needing unrestricted access to the underlying development environment.

16. Client Review & Feedback

While viewing the live preview, the client can identify anything they would like to change.

If the client has a concern about a particular section, design, functionality, or layout, they can provide feedback.

Where appropriate, we provide a remote review/feedback mechanism that allows the client to indicate the exact area they are referring to.

This makes feedback more precise and easier to understand.

The client can communicate things such as:

• Change this section
• Move this element
• Use a different design
• Change this image
• Adjust this layout
• Modify this functionality

We then review the feedback and make the appropriate changes according to the agreed scope.

17. Continuous Development & Updates

The project follows a continuous development cycle:

Development

Live Preview Update

Client Review

Client Feedback

Revision

Updated Preview

This process continues throughout development.

As a result, the client is not left wondering what is happening behind the scenes.

They can continuously see the project's progress.

18. Testing & Completion

When the agreed development work has been completed, we move toward final testing and completion.

The project is reviewed to make sure the agreed requirements have been implemented and the system is ready for final deployment.

Any remaining issues within the agreed scope are addressed before final delivery.

19. Final Approval & Deployment

Once the project is ready and the client has reviewed and approved the final version, the project moves to deployment.

The completed project is deployed to the client's actual production environment where applicable.

This may involve the final:

• Domain connection
• Hosting configuration
• Server configuration
• Database connection
• API configuration
• Integration setup
• Production deployment

The exact process depends on the project.

20. Full Access & Source Code Handover

After the project is completed, the client receives the appropriate full access and the source code.

Depending on the project, this may include:

• Website/CMS access
• Hosting access
• Server access
• Domain access
• Database access
• Source code
• Repository information
• API/integration information
• Deployment information
• Relevant documentation
• Other necessary project resources

The reason we provide the source code is straightforward:

The client becomes the owner of the delivered project.

The client should be able to manage the project independently and should not be technically locked into us simply because we built it.

21. No Hidden Access

We do not intentionally retain hidden or undisclosed access to the client's systems.

We do not keep secret administrator accounts, hidden credentials, backdoors, or undisclosed access mechanisms.

The client receives the relevant information and access necessary to understand and control their own project.

The objective is complete transparency.

22. Repository & Optional Maintenance

If the client chooses to continue with our maintenance service, we may retain a copy of the project's source code in our repository.

This helps us provide ongoing maintenance and support efficiently.

The repository can be useful for:

• Maintenance
• Bug fixing
• Future updates
• Troubleshooting
• Version control
• Backup/recovery
• Faster technical support

However, retaining a repository does not mean that we retain ownership of the project.

The client has already received the source code and relevant access.

23. If the Client Does Not Want Us to Keep the Repository

The client has the right to decide whether they want us to retain a copy of the project repository.

If they do not want us to keep it, we respect that decision and do not retain it according to the agreed handover process.

There is no requirement to continue using our maintenance service.

The client can manage the project independently or work with another provider.

24. Why We May Keep a Repository

If the client allows us to retain the repository, it gives us the ability to help them more efficiently in the future.

For example, a client may stop using our maintenance service and later return with a technical problem.

If we still have the relevant project repository, we may be able to review the existing codebase and attempt to solve the problem more efficiently.

We do not use the repository to prevent the client from working with another provider.

It is maintained primarily for continuity and support.

25. Access Revocation After Our Work Ends

When our active development or maintenance responsibility ends, unnecessary access should no longer remain active.

We ask the client to revoke our access to their systems when our access is no longer required.

This may include access to:

• Hosting
• Server
• Domain
• CMS
• Cloud platforms
• Third-party services
• Other project systems

This ensures that access remains limited to people who actually need it.

26. Exception: Ongoing Maintenance

If the client continues to use our maintenance service, the necessary access can remain active.

This is because we still need access to perform the agreed maintenance work.

As long as the maintenance relationship continues, appropriate access may remain active.

If the client stops the maintenance service, they can revoke our access.

27. The Client Remains in Control

Our overall approach can be summarized as:

The client owns the infrastructure.

The client controls the accounts.

The client authorizes access.

We use that access to perform the work.

The client can see the project progressing.

The client can provide feedback.

The client understands the scope, timeline, and budget.

The client receives the source code and required access at completion.

The client can revoke our access when our work is no longer required.

28. Two Communication Paths, One Transparent Process

Whether a client prefers meetings or email, the underlying project process remains transparent.

Meeting-Based Workflow

Lead Submission

→ Email/WhatsApp Contact

→ Calendly Meeting

→ 30-Minute Free Consultation

→ Quotation

→ Quotation Review

→ Optional Follow-up Meeting

→ Scope/Budget Agreement

→ Agreement & Signing

→ Payment

→ Client Portal

→ Development

→ Live Preview

→ Feedback

→ Revisions

→ Testing

→ Approval

→ Deployment

→ Full Access & Source Code

→ Optional Maintenance

Email-Based Workflow

Lead Submission

→ Email Communication

→ Requirements Discussion

→ Quotation

→ Email-Based Clarification/Negotiation

→ Agreement & Signing

→ Payment

→ Client Portal

→ Development

→ Live Preview

→ Feedback

→ Revisions

→ Testing

→ Approval

→ Deployment

→ Full Access & Source Code

→ Optional Maintenance

The client does not have to use Zoom or Google Meet if they prefer to handle everything digitally through email.

29. Why We Follow This Process

The reason for following this process is to ensure that the client is always acknowledged and informed.

A client should not have to repeatedly ask:

"What is happening?"

"How much of the work is complete?"

"Why does this cost this much?"

"What happens next?"

"Who owns the website?"

"Who has access?"

The live preview, client portal, email communication, quotations, agreements, and final handover are all designed to answer these questions through a transparent process.

30. Our Core Principle

At every stage, our goal is to maintain a clear relationship between:

Communication → Transparency → Authorized Access → Development → Client Feedback → Approval → Ownership

We believe the client should remain informed throughout the project and should ultimately have complete control over what they own.

We build it. You own it.

Whether the project is completed in a few weeks, several months, or six months or longer, the same principle applies:

**You know what is happening.

You know what you are paying for.

You can see the progress.

You can provide feedback.

You receive the final project and source code.

You control your accounts and infrastructure.

And you decide whether you want to continue with us for maintenance.**

That is the foundation of our project workflow: transparent, flexible, client-controlled, and accountable from beginning to end.