Project Intake

Project Requirements Checklist

Tell us about your business and the outcome you need. A straightforward company website is the recommended starting point for most organisations—you only need to select extras that solve a real need.

Step 1 of 7: Client Information 14% Complete

cloud_doneYour answers are saved automatically in this browser.

tips_and_updates

Keep it simple and accurate

This is a scoping guide, not a test. Choose only what your business needs now. “Not sure” is a useful answer—our team will advise you before pricing.

1. Your contact details

Who should we speak to about this request?

Your full name *

Phone

2. About the company

This helps us write and design for the right audience. Short, factual answers are enough.

Company / organisation name *

Industry *

What does the company do? *

Mention your main products or services, location, typical customers, and what sets you apart.

Existing website

Company profile (optional)

Upload your current profile if it already explains the business. PDF, Word, or PowerPoint; maximum 10 MB.

3. What are we building?

Focus on the business result. We can recommend the technology.

Project name *

Desired outcome *

In 2–4 sentences: what problem should this solve, who is it for, and what should visitors be able to do?

Website size

Helps us estimate cost

Choose the closest fit. You can change this after consultation.

5-page company website RecommendedUsually Home, About, Services, Projects/Portfolio, and Contact. 1-page websiteA concise scrolling page for a small business, campaign, or simple online presence. More than 5 pages / customFor a larger content site, portal, shop, booking system, or web application. Not sure yetTell us the outcome and we’ll recommend the smallest sensible option.

route

On this step: choose the simplest fit

Confirm what you are building, where people will use it, and who those people are. The recommended website choices are already selected; change them only if your project genuinely needs something different.

4. Solution type

Select the main thing you need. For most businesses, choose Basic Company Website only.

Basic Company Website E-Commerce / Online Store Web Application Mobile App (iOS) Mobile App (Android) Learning Platform CRM / Business System Virtual or Augmented Reality 3D Visualization / Digital Twin Not Sure — Advise Me

5. Where should it work?

A normal website already adapts to phones and computers. Select mobile apps only if users must install an app.

Responsive Website (Phone + Computer) Android App iPhone / iPad App VR Headset Not Sure — Advise Me

6. Target Users

Describe the people you want to reach—not “everyone.” Think about who is most likely to visit and what they need.

Primary audience *

A useful answer includes the customer type, location or market, and reason for visiting.

Other user groups (optional)

Example audiences — click to use

Website features

Start with the essentials. Optional features can increase build time and cost, so select one only when you can explain how it will be used.

language

Basic website essentials

Recommended

A professional informational website normally needs these. Select all that apply; content and contact details are still supplied by you.

Mobile-friendly design

About & services pages

Contact form

Google Maps location

Social media links

Basic search visibility (SEO)

extension

Optional add-ons

Leave these blank unless they support a real process. For example, choose payments only if customers must pay on the site.

Online payments

Online store

Appointment booking

Customer accounts

Live chat

Multiple languages

Email newsletter signup

Advanced analytics dashboard

Push notifications

AI chatbot

Member portal

Video conferencing

3D or VR experience

11. Key Functional Needs

help

Describe actions, not technology

Ask: “What must a visitor or staff member be able to accomplish?” You do not need to know technical terms. One clear sentence is enough.

What must visitors be able to do? *

Describe an outcome, not technical jargon.

Useful later (optional)

Reporting (optional)

Must-have examples — click the closest one, then edit it

tune

Most basic websites can skip this step

Only select a connection if the website must exchange information or payments with another service. Leave compliance standards blank unless your organisation already knows they apply.

9. Payments & integrations

Choose only services the website must connect to. A normal enquiry website does not need a payment gateway.

payments

Payments in Zimbabwe

No online payments — enquiries only Paynow — EcoCash / OneMoney / cards Pesepay — local payment options Zimbabwe bank transfer / proof of payment Advise me on the best Zimbabwe option

public

International payments

Select these only if you have—or can open—a supported merchant account for the countries involved.

PayPalStripeInternational card paymentsMulti-currency checkout

add_circleOther business integrations

Calendar (Google/Outlook)CRM (Salesforce/HubSpot)Video Conferencing (Zoom)Social Media APIsCloud ServicesIoT Devices

13. Compliance & security

Do not select a standard just because it appears here. Choose it only when a regulator, contract, industry, or client requires it.

POPIAGDPRPCI DSSHIPAAISO 27001SOC 2Not sure — advise me

verified_user

Standard website security is included

Secure hosting configuration, HTTPS, form protection, and sensible access controls will be considered without you choosing a certification.

Modern browser support

Recommended browsers are selected by default. Untick one only if you have a specific restriction.

ChromeFirefoxSafariEdge

support_agent

Choose what you will genuinely use

A basic company website usually needs a clean handover and help when requested—not a costly 24/7 contract. Your selection helps us quote the right level; it does not automatically commit you to a support plan.

18. Support after launch

Select one starting point. We will confirm the exact coverage, response times and price in the proposal.

Launch handover onlyRecommended for basic sites

Training and handover, then request and approve help only when it is needed.

Monthly website care

Scheduled updates, routine checks and a predictable monthly arrangement.

Managed growth support

Ongoing content, performance and improvement work for an active website.

Critical 24/7 supportEnterprise add-on

For systems where downtime directly stops operations; requires an agreed SLA.

What may need ongoing help? Optional

Content changesSecurity & software updatesBackups & recoveryPerformance monitoringStaff trainingNot sure — advise me

Support expectations Optional

21. How we work with you

One available decision-maker keeps approvals moving and protects your launch date.

Primary project contact *

Final approver

Who can approve scope, content and launch?

Preferred channel *

Update rhythm *

Best time to reach you

Existing collaboration tools Optional

schedule

Clear expectations: routine communication happens during agreed business hours. After-hours or guaranteed response times apply only where a support SLA is quoted and accepted.

event_available

How scheduling and priority work

Your requested launch date helps us check the delivery calendar, but it is not a booking yet. Project priority is based on four things: completed requirements, the agreed payment or deposit, the expected launch date, and available team capacity.

Minimum window: at least 2 days between kickoff and launch—one day for development and one day for testing. Larger or more complex projects will need more time.

4. Timeline

Choose realistic dates rather than the earliest possible dates. We will check them against current projects and confirm the schedule in your proposal.

Project Kickoff *

When your content, approvals, and project contact will be ready.

MVP / First Review *

When you need the first usable version for review—not necessarily the final launch.

Expected Full Launch *

Your preferred go-live date. It remains provisional until scheduling and payment are confirmed.

calendar_month

Select all three dates to check the delivery calendar.

20. Budget & Delivery Plan

Share a realistic range so we can recommend the right scope. This is not a commitment or final quotation.

Preferred currency *

Working budget range *

How should we approach delivery? *

Launch essentials first RecommendedStart with the smallest useful website, then add improvements after launch. Deliver everything in one phaseBest when the full scope and budget are already approved. Recommend phases for meWe will separate must-haves from later enhancements.

Payment readiness *

This helps us plan capacity; it does not pressure you to pay before approving a proposal.

Your budget priorities or constraints

Tell us what must fit now, what can wait, and any approval or funding conditions.

14. How Should the Website Create Value?

Most company websites do not charge users directly. Choose how this project should support the business.

No direct monetization Typical company websiteGenerate trust, enquiries, calls, visits, or quotation requests. Sell products or services onlineCustomers pay per order, booking, or service. Subscriptions or membershipsCustomers pay repeatedly for access or benefits. Advertising or sponsorshipRevenue comes from advertisers, sponsors, or listings. Another business modelDescribe your intended model below.

How should it work? (optional)

Describe the customer journey in your own words. Leave blank for a standard informational website.

verified

Ready to Launch!

You've completed the automated requirements intake. Any final notes before we submit this to our engineering team?

Additional Requirements

I have reviewed the scope, priorities, timeline and budget information above. I understand Smart Pulse Africa will validate feasibility before issuing a final proposal.

info

By submitting this form, you are providing Smart Pulse Africa with the initial data needed for project scoping. This document is confidential and will be used solely for the purpose of architectural design and proposal creation.

SMART PULSE AFRICA