Process
There is no queue, no account manager and no committee. You send a request, I read it, and if it is a yes we plan, build and hand over together. This page explains each step, what I ask of you along the way, and how the invitation and approval part works.
Most work takes four to twelve weeks from the first plan. Larger applications are broken into stages so something useful is live early.
Step by step
Ten minutes on the get started form. Who you are, whom you serve, where, and what is getting in the way online. Plain words are best. You do not need to know what a website should cost or what "SEO" means.
If you have anything already, a website, a Facebook page, a Google listing, give me the link. If you have nothing, say so. Both are fine.
Every request lands with me, not a form-handler. I read it, look at what you have online today, sometimes search your name the way a stranger would, and ask one question: is this work service to others, and would a proper digital presence help it?
You get one of three answers. Yes, with an invitation to the ProSeva console and a suggestion for where to start. Not yet, with a rough idea of when to ask again. Or no, with the reason. I do not leave requests unanswered.
One conversation, on a call or in writing, whichever suits you. I tell you what I see, what I would do first and why, and what I would leave alone. You tell me what matters most to the people you serve. We write it down in the console so both of us can see it.
This is also where the practical things get settled: who owns the domain, who is my point of contact, what content you have and what needs writing, and any third-party costs, which are always small and always explained before they happen.
You see progress in the console as it happens, not as a surprise at the end. I show you early versions, ask when I am unsure, and adjust. Work goes at the pace your organisation can absorb, because a site nobody has time to check is a site that ships with mistakes.
Everything is built on plain, standard technology, in accounts that belong to you. There is no ProSeva lock-in, by design. If I disappeared tomorrow, any competent developer could pick it up from the documentation.
When the work is done I hand over every login, every account and every document, and walk you through how to make the everyday changes yourself. Domains, hosting, code, content: in your name, from day one, so there is nothing to transfer later.
Then I step back, but I stay reachable. If something breaks or you need the next thing, you can ask again. You are equally free to take everything to anyone else and lose nothing.
Requests and invitations
Anyone whose work serves others can send a request through this site. Separately, when I come across an organisation doing good work that is hard to find online, I write to them and invite them. Both paths lead to the same place: a plain answer from me, and if it is a yes, access to the ProSeva console where the work is planned and tracked.
Approval is a real step, not a formality. One person does everything here, so I take up only what I can finish well. That means the honest answer is sometimes "not yet". It is not a judgement on your work. It is a limit on my hours, and you are welcome to ask again later.
Requests are read within two days. Invitations are personal. Neither is automated.
Send a request through the get started page. It takes about ten minutes and you hear back within two days.
If I write to you first, it is because I have seen your work and think I can help. There is no obligation, and the process from there is the same.
When I am full I say so, and tell you roughly when to check back. I keep a short list, and I do get to it.
Who qualifies, and who does notHow I work
If I cannot do something well, or do not have the time, I say so, and where possible point you to someone who can.
Plain, well-documented, standard technology that the next person can maintain without me.
Domains, hosting, accounts and code in your name. You can walk away at any point and lose nothing.
I do not guarantee rankings, traffic or donations. I show you the direction of change, truthfully.
You hear back on your request within two days. After that, a first website with the essentials usually takes four to eight weeks, mostly waiting on content and decisions from your side. Applications take longer and are built in stages, so something useful is live early. I tell you the likely timeline in the plan, and I tell you again if it changes.
A private space at console.proseva.org where the plan, progress, decisions and documents for your work live. You get access when a request is approved. It is how you see what I am doing without having to ask, and how we both remember what we agreed.
Less than you fear, but not none. Plan for one conversation at the start, a few short questions along the way, and a couple of hours to gather facts, photos and to read what I write about you. The organisations that get the most out of this are the ones where one person is clearly responsible for answering me.
No. Everything is yours, and you decide what to keep. If a tool does not fit how you actually work, tell me and we change it or switch it off. I would rather build less that gets used than more that sits idle.
Ask. You are not tied to me, but you are not cut off either. Small fixes I do when I can. Bigger next steps go through the same honest review as the first request, because my hours are the same finite thing they were before.
Begin
