Customer portals
Logins, roles, documents, order history and invoices behind one account, with signed download links and an audit log.
laravel, livewire, pdf exportCustom web development when a template is not enough
Portals, booking systems, customer dashboards and APIs, built in PHP and Laravel by default or in the stack your team already uses. I run the Linux servers they live on too. Paid discovery from €490, credited to the build; web apps from €8,000.
from€490paid discovery, credited to the build. Web apps from €8,000, excl. VAT 25.5 %.proposed
1. what do you need?
2. your team already works in
3. constraints
recommended stackexample, confirmed in discovery
Laravel + MySQL / MariaDB + Redis queue on a VPS
- Customers log in and see their own data, so roles, password resets and an audit log come first.
- Laravel is widely used, well documented and easy for another PHP developer to pick up later.
Check first whether the software you already use sells a customer portal module. If it does and it fits, buy it.
Effort band120–220 habout €11,400 to €20,900 excl. VAT at €95/hexample
Send this stack with my quote request
Stack names are plain text. Pikselipolku is an independent studio and is not affiliated with Laravel, WordPress or any other framework or product named here.
The handover kit: eight things you receive with every build
Custom code is only yours if someone else could run it tomorrow. Tick what your current project already has, and open each item to see a sample of what I deliver.
Git repository in your accountevery change, with a message
READMEREADME.md
Environment file template.env.example
Deploy scriptdeploy.sh
Database migrationsdatabase/migrations/…_create_bookings_table.php
Tests for critical pathstests/Feature/BookingTest.php
Admin documentationdocs/admin.md
Access listdocs/ACCESS.md
README.mdsample
# client-portal ## Run it locally cp .env.example .env composer install php artisan key:generate php artisan migrate --seed ## Deploy ./deploy.sh production
How to run, test and deploy the project, written for the next developer, who may not be me.
1 of 8in your current project
Today the project depends on someone remembering how it works. Producing the missing items is the first job of a takeover.
What gets built this way
Jobs where a theme or a plugin stops fitting. Each one runs on a server I set up and look after, so the code and the hosting are tuned together.
Booking systems
Availability rules, slot locking that stops double bookings, reminders by email or SMS, and payments through your provider.
queues, scheduler, webhooksInternal tools
The spreadsheet your team outgrew, rebuilt as admin screens with permissions, history and exports your accountant can read.
admin panel, csv, rolesAPIs and integrations
Connect two systems, or open your data to a partner, with token auth, idempotent webhooks, retries and a failed-job log.
rest, openapi, retriesCustom features on existing sites
A price calculator, configurator or member area added as your own documented plugin or package, not a pile of add-ons.
wordpress plugin, php packageTakeovers
A site another developer built, brought under version control, documented, upgraded to a supported PHP version and made deployable.
audit, git, php upgradedefault stack, where I deliver fastest
- PHP 8.3+
- Laravel
- WordPress
- MySQL / MariaDB
- Redis
- Nginx on Debian or Ubuntu
on demand, when your team uses it
- Node.js
- Python and Django
- React
- Vue
- PostgreSQL
Prices for custom work
Euros, excluding VAT 25.5 %. Every build starts with paid discovery, so the fixed quote is based on a written spec rather than a guess. proposed owner to confirm
Discovery
A workshop, a written spec and a fixed quote.
from€490credited to the build
- Requirements and user roles
- Data model and integrations list
- Stack choice with reasons
- Fixed quote per phase
- The spec is yours, even if you stop here
Recommended
Custom web app or MVP
Portal, booking system, internal tool or dashboard.
from€8,000fixed per phase, excl. VAT
- Phase one live on a staging URL first
- Tests for the critical paths
- Server set-up and deploy script
- The full handover kit
- 30 days of fixes after launch
Small feature or fix
One feature, plugin, report or bug, on an existing site.
from€690fixed, excl. VAT
- Written scope before work starts
- Built on a copy, not on the live site
- Committed to your repository
- Short note on what changed
Hourly work €95 (+50 % out of hours). Maintenance after launch: €79, €199 or €449 a month with 1, 3 or 8 hours included, covering hosting, updates, backups and monitoring. A larger app is split into phases, each with its own fixed price, so you can stop after any phase and keep everything built so far.
Have a spec, or only a problem and a spreadsheet? Either is a good place to start.
Get a custom build quoteWhen I would not build it custom
Custom code has to be hosted, updated and understood for years. Sometimes that cost is not worth it.
- 01A subscription product already does nine-tenths of what you need, for less than a year of maintenance on a custom build. I will point you to it and help you set it up.
- 02Your marketing site only needs pages and forms you can edit. WordPress with a lean theme is cheaper and easier to hand over.
- 03The product needs several developers and round-the-clock on-call support from day one. I work alone, so I will say so and help you write the brief for a team.
From problem to running software
Each phase ends with something working that you can click through before the next one is priced.
- 1
Discovery
Workshop, user roles, data model and a written spec, from €490.
- 2
Fixed quote
A price per phase, with the stack and its reasons in writing.
- 3
Build in phases
Staging URL from week one and a short demo at each milestone.
- 4
Launch and hand over
Deploy, backups, monitoring and the eight-part handover kit.
- 5
Run it
A maintenance plan with me, or your own team using the kit.
Questions about custom builds
Which language and framework will you use?
PHP with Laravel by default, because that is where I deliver fastest and the Linux servers I run are tuned for it. If your team already works in another stack, such as Node.js or Python, I build in that on demand so your developers can maintain it. The discovery spec names the stack and why.
Do I own the code?
Yes. The code lives in a Git repository in your own account from the first commit, and it is yours outright on final payment. Open-source frameworks keep their own licences. The handover kit includes a README, environment template, deploy script and access list, so another developer can take over without me.
Can you take over a site another developer built?
Usually, yes. I start with a paid review: get the code running on a staging server, check versions, security and missing documentation, and tell you in writing what to keep, fix or rewrite. If there is no repository or no tests, producing the handover kit becomes the first job.
Get a custom build quote
Describe what the software should do and who will use it. You get a written reply within one working day with the next step and a price for discovery.
Stack from the bench above: not sent yet (use the link under the recommendation)
If you stop after discovery, you keep the spec and can take it to any developer.
Prefer email? Write to hei@pikselipolku.fi
Pikselipolku is an independent studio and is not affiliated with Laravel, WordPress or any other framework or product named here.