Public website feature · not an authenticated platform screen
Explore by country
The public country explorer demonstrates structured information and an interface built around exploration.
Explore the caseNexney / Business systems & automation
One idea. A practical next step.Less chasing information. More useful work.
Show me the process that keeps slowing you down. We can map it, connect the right tools and build a useful first version around the people doing the work.
Name, email and your idea. Write as much as you need.
Africa Circular · public country explorer
- Workflow discovery
- Practical integrations
- Human review
A useful starting point
Sound familiar?
You do not need a finished brief to start. A real problem and a rough idea are enough for the first conversation.
Your team copies the same information between several tools.
Files, emails and spreadsheets make a process hard to follow.
You need to prove one useful workflow before investing in a larger system.
The work / A closer look
Make information easier to explore.
The public Africa Circular website shows how complex information can become understandable screens and clear routes. It is one visible part of the wider website, platform and workflow work.
Public article archive · no private records shown
Find a useful route in
The public article archive gives visitors a route into content. These screens demonstrate information design, rather than private business-system behaviour.
Explore the caseThese examples show the work and its stated delivery status. Measured sales or enquiry improvements are not claimed. Project cases include contribution and AI-assistance details.
What we can make
Start with one process worth improving.
A clear scope before the work starts. A useful result you can review.
Map the work.
Understand the people, inputs, decisions and handovers. Agree what a useful improvement would look like.
Prove a focused first version.
Use representative examples to test a small end-to-end journey before extending the scope.
Connect tools with care.
Assess the APIs and access available, then build the agreed integration with checks and understandable failure handling.
Keep people in the loop.
Make review, ownership and operating instructions part of the work. Where AI is useful, agree what needs a human decision.
Discovery comes first. The quotation defines the workflow, access, integrations, review points and acceptance checks. Third-party services and running costs are identified separately. The public examples below demonstrate information design; private platform workflows and their performance are not presented as public evidence.
Your idea, in your words
Send what you have.
We’ll shape it together.
Describe what happens now, which tools are involved, who uses them and where work gets stuck. Start with an anonymised example or a description; we can agree suitable access later.
Discuss my workflow by emailYou work directly with Marshall
Human conversation.
Practical progress.
I bring design, development and content together, using AI where it supports the work. You review the direction, and we agree the next step before moving on.
Meet MarshallStart by email.
Send your idea in one message. Add links or creative material if you have them.
Agree the job.
I review the brief and come back with questions, a practical scope and a quotation.
Build, review and hand over.
See the work at agreed points, check the result and decide whether you need ongoing help.
After the first project / Ongoing support
A useful system needs continuing attention.
After the first workflow is accepted, put operational questions and improvements into a shared priority list with a clear owner on each side.
Examples for the priority list
- Review a recurring failure and improve its handling.
- Adapt a form or integration when the process changes.
- Update operating instructions and test an agreed improvement.
A working agreement, made clear
- Capacity & priorities
- Agree monthly capacity, support hours and response expectations. Keep one prioritised list and confirm what fits before work starts.
- A regular review
- Agree a regular review of completed work, open issues and the next improvements. Planned development and urgent support have separate expectations in the agreement.
- Ownership & handover
- Agree who owns the files and accounts, who maintains them and how work is handed over. Identify third-party costs and any larger new projects separately.
The quotation defines the fee and the arrangement. Ongoing support is a separate choice after a project, with its own scope.
Optional / Nexney Kickstarter
Bring your direction.
Get 10% off your quoted project fee.
Add your brand details, palette, logo or references through the Kickstarter in the enquiry form. We agree the scope and confirm the discount in your quotation. Sending an enquiry does not commit you to a project.
Start with the KickstarterBefore you start
A few useful answers.
Do I need to know which system to build?
No. Start with a specific problem and someone who understands the current process. Discovery turns that into a practical scope.
Can you connect the tools we already use?
Often, but it depends on their APIs, permissions and subscription limits. I check those before promising an integration.
Does every workflow need AI?
No. A clear form, a better data structure or a straightforward integration may solve the problem. AI is considered only where it serves the agreed task.
Can I share private documents in the first email?
An anonymised example or description is enough to start. We agree appropriate access and handling before working with sensitive material.
Your next journey
Which part of your work could flow better?
Send your idea in your own words. I’ll reply by email and help work out the next step.
Discuss my workflow by email One conversation to start. Scope and price agreed before work begins.