Questions before you commission a specialist website or platform.
Clear answers about scope, ownership, growth, technology and international operations. Where a question needs its own method or examples, follow the linked guide.
Start with the service you can deliver.
Do I need a website, a booking tool, a hotline or a marketplace?
A solo practitioner usually needs a clear offer, trust information and a complete enquiry or booking path. A hotline adds live reader availability, call routing, billing and support. A marketplace adds reader onboarding, discovery, payouts and disputes. Map one paying customer journey and the team that fulfils it before buying a large feature list.
See the launch checklist, hotline guide and marketplace validation guide.
Should I begin with WhatsApp, a calendar or checkout?
Use the channel that the team can respond to reliably and that fits the promise. WhatsApp may suit a considered first conversation, a calendar suits predictable appointment inventory, and checkout suits a clearly specified paid offer. If a visitor can click but no one handles the response, adding more buttons will not fix the journey. Test a real enquiry and its follow-up owner.
Can I move a tarot or astrology business away from a marketplace?
Often a practitioner can create an owned site for future acquisition and repeat clients, subject to the marketplace's terms and the customer's consent. Do not assume you can export customer contact details or reviews. Plan how new buyers will find the site, what booking and payment workflow replaces the platform, and how ongoing customers will be served during transition.
Ask for the handover in the proposal.
When is WordPress enough and when is custom software justified?
A conventional practitioner site with content, scheduling and a few integrations can often use a maintained CMS and established tools. Custom software becomes a stronger case when availability, routing, pricing, calculations, permissions or settlement rules cannot be supported reliably by those tools. Compare the total operating cost, support owner and change process, not only initial design cost.
Who should own the domain, design files, content and analytics?
Agree account and asset ownership before implementation. The business should know who controls its domain, hosting, code or theme, editable content, analytics, payment and telephony accounts, and data exports. Contracts may distinguish pre-existing vendor components from project-specific work. Ask for access, documentation and an exit or migration path in writing. The agency comparison guide includes a handover scorecard.
How do astrology API integrations affect scope?
Separate input data, calculation coverage, report or chart interpretation, API licensing, response times, caching, error handling and support. A demo with one birth chart does not prove coverage of unknown time, location ambiguity or compatibility rules. Test sample inputs, output and failure states before choosing a vendor. See the API selection guide.
What should a project estimate include?
Ask for deliverables, content responsibilities, integrations, acceptance tests, handover, hosting or support, change control and third-party costs. Advertising spend, telephony and payment fees need separate treatment. A universal “psychic website price” cannot fairly represent a brochure site and a multi-reader live platform. Explore engagement models and the scope tool.
Separate reach from qualified demand.
Will 20 blog posts make a new site rank?
There is no dependable page count. Publish a page when it answers a distinct question with an example, method or evidence that a qualified owner can maintain. Improve the core offer and enquiry experience first, then add articles based on customer questions and Search Console evidence. Near-identical country, city or question pages built mainly for similar searches increase spam and quality risk. Read the SEO architecture guide.
Should I make a page for every city or country?
Only when availability, language, service, support, payment or local context changes enough to help that visitor. Start with the international market framework. A global offer does not need five near-identical country pages. If separate language or regional versions are warranted, maintain the whole journey and use correct technical signals.
Can an agency guarantee Google rankings or leads?
No. An agency can research demand, improve site accessibility and technical health, develop useful pages, measure qualified enquiries and report changes. Search engines choose what to crawl, index and show. Lead volume also depends on offer, competition, follow-up and fulfilment. Agree on a lead definition and measure the whole path rather than buying a ranking promise.
How should calls and WhatsApp enquiries be measured?
Instrument the click, but distinguish a click from a connected call, received message and qualified opportunity. Record source, landing page, project type, response time and eventual outcome with appropriate consent. Review search terms and lead quality for paid campaigns; a rising count of unqualified clicks is not growth.
Know exactly what happens next.
What should I send SoulGait for a useful first conversation?
Send your service and target buyer, current website or process, first market, the action a customer should complete, the failure you see today and an investment or timing range if known. A screenshot of the current booking or support workflow often reveals more than a long feature list. Use the project brief or contact us directly.
What happens after I send a project brief?
We review your goals, scope, timing and the customer journey you want to improve. We then reply using the contact details you provided with clarifying questions or a suggested next conversation. Sending a brief does not book a meeting or commit you to a project.
What should I include for a useful first discussion?
Tell us what you sell, who it serves, what should happen when a visitor contacts or books you, and what is not working today. Include any existing website, booking or payment tools and your preferred timing. You can leave unknown technical choices open; we can discuss them after understanding the business goal.
If your concern requires a different answer, describe the service and the constraint. Tell us which decision is difficult or which step in the customer journey is failing. Prepare a brief ↗
Turn a broad idea into a reviewable brief.
Write down the first action a customer must complete, who fulfils it and what evidence will show that it worked. For a solo consultation, this may be a confirmed appointment with the correct local time and a reply route. For a store, it may be a paid order that the team can fulfil and refund. For a reader platform, it may include a completed call, a reader payout record and a support path for a failed connection.
Then separate decisions from features. Decide whether people choose a named practitioner or the next available one; whether payment comes before approval; whether an existing calendar, CMS or telephony system must be retained; and who owns the data and accounts. Ask a supplier to show the normal path and at least one failure path. A proposal is easier to compare when it names deliverables, responsibilities, third-party costs and handover conditions.
If you are unsure which question applies, begin with the service you can deliver now. The detailed guides below the answers cover booking, platform validation, search architecture and launch checks when you need to go further.
Explore the full resources library.
Further reading on search quality: Google people-first content, doorway policy. Project scope, responsibilities and commercial terms are confirmed in a written agreement.