Plugins and extensions
Is your website or e-shop missing one important feature? We check whether an existing plugin, a change, an integration or a custom add-on is the right fit. A new website is not automatically needed.
Adding the missing piece is cheaper than a new website
Websites and e-shops rarely fail as a whole. One thing fails: a listing that cannot be filtered, data retyped from another system by hand, or staff doing the same thing every week because the site cannot.
That brief does not need a new build. We write an add-on that plugs into the site, is configured in the admin and does exactly the one thing that is missing.
First, though, we check whether a similar add-on already exists. If it does, we will recommend it.
What your own add-on brings
The missing feature, not a new site
The website or e-shop stays. We add only the part that is missing. The price matches the scope of the add-on, not a new build.
Data from elsewhere without retyping
The add-on can pull listings, price lists or availability from another system and keep them current.
Administration where you are used to it
Settings live in the website admin. No second system to learn and no extra login.
Costs that match the real scope
You pay for developing the add-on by its scope, with no automatic subscription, if that is what we agree in the offer. Hosting, site maintenance and third-party licences are handled separately.
Rules that match you
Off-the-shelf plugins offer what they can do. A custom add-on does what you need, including the exceptions in your operation.
Maintenance and updates
On sites we look after, we watch add-ons through platform updates so a new version does not break something.
Add-ons we have written
Spolu v realitách: listings on the website without retypingProperties, photos and code lists update themselves from POSKI REAL.
Screeno: custom booking instead of an off-the-shelf systemSlot availability, workshops, vouchers and a link to WooCommerce.
Art of Život: a marketplace with its own vendor managementVendors, product ownership and payment splitting through Stripe.How the work goes
Every stage has an output we agree on.
What it has to do
We describe the feature and go through where it touches the operation. We also find out whether a similar solution already exists.
Output: A description of the feature and where it touches your operations.
Checking what is possible
We verify what the platform and the connected services allow. If the road is a dead end, we find out now, not after weeks.
Output: A check of whether the solution works on your platform.
Development and testing
We develop the add-on on a test site. You try it before it touches production.
Output: The extension on a test site for you to try.
Deployment and maintenance
We hand over access, documentation and source code to the extent we settle in the offer and the contract before the work starts. We deploy to the live site and watch the first days. After that only updates and additions.
Output: The extension on your live website.
What we choose from
The add-on has to fit the platform the site runs on. We choose the tools accordingly.
Three scopes we meet most often
The prices for each scope are indicative lower bounds from the calculator, excluding VAT. They are not an offer: we prepare an exact price once the brief is clear.
One feature
One specific missing thing: a form, a listing, an export, a change in the cart. The fastest route to a result.
- Checking what is possible
- Development and deployment
- Settings in the admin
A link to another system
Pulling data from an external service and keeping it up to date. The most common scope.
- Review of the interface
- Synchronisation and mapping
- Scheduled runs and logs
- Error handling
A module for the operation
Bookings, accounts, approvals. An add-on that brings a whole process into the site.
- Screen design
- Roles and permissions
- A link to payments
- Development after launch
We will say when you do not need us
A good plugin exists
When a ready-made add-on does what you need, we will recommend it and help with the setup. Development would not pay off.
The site is at the end of its life
On very old installations an add-on props up something that will be rebuilt anyway. We will say when a new site is the better spend.
You want to get around the platform
Sometimes a feature works against how the platform behaves. Such an add-on breaks at the first update and we will not build it.
What the add-on connects to
What you ask before building an add-on
Did not find your answer? Write to us and we will reply within two business days.
How much does a custom plugin cost?
The price follows what the add-on has to do and what it connects to. One feature is usually days of work, a module for the operation weeks. You get an estimate after the first call.
Do you only work with WordPress?
Most often yes, because most of the sites we develop run on it. But we also write add-ons for e-shops and internal applications on other platforms.
What happens when the platform updates?
We build add-ons to survive updates, and on projects we maintain we check them after an update. When the platform changes behaviour, we adjust them.
Will you connect the add-on to our system?
If it has an interface or an export, yes. With older systems we check first and say what is possible before development starts.
Can we use the add-on on more websites?
That depends on what we agree in the contract. When we hand over the rights to the code, you can deploy it elsewhere too. Licences for third-party services follow their own terms.
Who owns the add-on?
We agree it in the contract before the work starts: who owns the code, whose accounts it runs on and what exactly we hand over.
Tell us what your website is missing
We check whether an add-on can do it and give you scope and price. We reply within two business days and suggest the next step.