Your first questions.
Before a tool goes on your site, you’ll want to know a few things. Here they are, answered in full.
Will it work for my trade?
We still have to come and look.
Of course. The tool doesn’t replace the visit; it shows which enquiries are worth one. It says out loud what it can’t know from what your customer typed, and that is what you look at on site.
Every job we do is different.
That’s why it runs on your rules, not on a template. Your customer answers what they can see about their own situation; the tool works out the rest the way you would, and names what it can’t know.
What if my customer can’t answer a question?
It asks what they can see, never your trade’s word: how big the hall is, how many people work there. Where they really don’t know, they say so: the estimate gets wider, and the tool carries on.
When is a tool the wrong answer?
When few people come to the site. Then nobody answers the questions, and the tool doesn’t pay. And when what your customer wants is simply a row in a list, a filter does it for less. If something has to be measured, with a logger or a site visit, no form can supply it. Perqli says so before quoting.
What it asks of you
I don’t have time for a project.
Little work, not none. Half an hour to explain how you work out a price. Then you try the tool and Perqli refines it, over a few rounds, until it’s right. More only when the rules live in one head, or three people have to agree.
We just had our site rebuilt.
Keep it. The tool goes in with one line of code, on WordPress, Wix or whatever your site runs on. It takes on your site’s look, and your site stays as it is.
Who writes the rules down?
Perqli does. You explain how you work out a price; Perqli writes it down and builds it, then you check that it answers the way you would. A working Excel helps. Your head is fine too.
What do I get when a customer sends it?
Every answer they gave, in your mail, and from a combination on in your CRM too. So your call can start on the details, like colour or material.
What it costs
What does my price depend on?
On how much the tool works out. More questions, more rules, answers that depend on each other, a link to your systems: more to build, a higher price. Your quote names one fixed price up front, and why.
What if it needs changing after launch?
For four weeks after launch, Perqli watches how it’s used and adjusts it, inside the build price. Prices you change yourself from Plus on, products and texts from Complete. Anything beyond what you first asked for, you talk through with Perqli.
I don’t want my prices on my site.
Then they don’t show. The tool can end in what fits their situation, without an amount, and you price it yourself. Showing prices is your choice, and you can change it later.
What’s yours
What do I get, exactly?
You get the code. Change it, run it yourself, take it to another developer: all allowed, without asking. Only reselling it or licensing it to others isn’t, because Perqli keeps the rights to what it builds. Your rules, prices and data stay yours.
Do I have to take a plan?
No. Without one you get the code and run it yourself, or hand it to a developer you choose. With one, Perqli runs it: hosting, updates, and the prices you send.
May Perqli reuse what it builds?
Yes, the code. Not your rules, prices or data: those stay yours and go nowhere else.
Didn’t find yours? Work out your own case, or ask Perqli.