Loading, please wait
Every project runs through the same four stages. You always know what happens, what PJX needs and what you get.
PJX replies to your inquiry by email.
A call to understand the business and the problem.
A written scope, timeline and quote to review.
A conversation about your business and what's in the way.
It starts with your inquiry and a call. PJX asks how the work gets done today, who's involved and what a good outcome looks like. If software isn't the answer, you'll hear it here.
A short written summary of the problem and whether PJX is a fit.
A written scope: what gets built, the cost and the date.
PJX turns the discovery notes into a proposal listing features, timeline and price. Nothing is built until you've agreed.
A plain-language scope, timeline and quote, agreed in writing.
Design first, then the build, with a preview link throughout.
You see the design direction before any code. During the build you get regular updates and a private preview link, so feedback lands while changes are still cheap.
A working preview that becomes the finished product, with every decision recorded.
Go-live, handover and support while real use settles in.
PJX tests on real devices, moves everything to accounts in your name and launches. A support window covers fixes and small adjustments. Further work is scoped separately, before it starts.
The live product, source code, documentation and every account, all yours.
The quote comes with the written scope. Scope changes are priced before they're built.
Dates depend on what's being built and are written into the proposal.
A private preview link and regular written updates. You never have to ask.
Code, accounts, domain and data are in your name, or transferred at handover.
A few sentences is enough. You'll get a direct, honest reply on whether and how PJX can help.
Discuss a Project