Customer portals
Portals, marketplaces and internal systems with clear roles and permissions, so every user sees and changes only what they should. Access rules and login options, including single sign-on, are designed in the first week.
PN Scripts · Web development
Customer portals, online platforms, e-shops, APIs and integrations in any stack: PHP, JavaScript and TypeScript, Python, Go, Java or .NET. You own the code, the accounts and the documentation from day one.
The standard
We build in the stack that fits the project, from PHP, JavaScript and Python to Go, Java and .NET. Payments, logins, data and every API endpoint get automated tests, and the documentation stays current. The code is organized so your team, or anyone you hire later, can extend it without starting over.
What we build
Six areas of work, from a new customer portal to taking over code another team wrote.
Portals, marketplaces and internal systems with clear roles and permissions, so every user sees and changes only what they should. Access rules and login options, including single sign-on, are designed in the first week.
APIs your web app, mobile app and partners can rely on: token or OAuth 2.0 authentication, versioned endpoints and OpenAPI documentation. We connect payment providers, booking systems, ERP and CRM through their APIs and webhooks, with retries, logs and alerts when a call fails. Every integration has automated tests and is documented for your team.
Fast loading, clean markup and structured data that search engines understand, from the first template. Error tracking and uptime monitoring are live before launch.
We review existing code in any stack, give you a written report and upgrade it in stages while your business keeps running. We can start with one critical part, such as payments or an outdated API.
We turn your designers’ work into a component library in Tailwind or your own framework. Every screen works with a keyboard and has readable contrast before it ships.
Deployed on PN Scripts Hosting, hosting from the same company, or on your cloud, with automated deploys, backups, background jobs, monitoring and written instructions for whoever operates it.
The request
We design, build and hand over every layer below.
01 · Browser
Responsive, accessible screens in the front-end technology that fits, fast from the first visit.
02 · Any back end
Authentication and business rules decide what each user is allowed to see and do.
03 · Third-party APIs
Payments, bookings, ERP and CRM connect through versioned APIs and signed webhooks, with retries when the other side is down.
04 · Background work
Slow tasks run in the background, so pages stay fast during traffic peaks.
05 · Storage
A database structure planned for the next feature, not just this one.
06 · Hosting
Deployment, backups, monitoring and alerts on PN Scripts Hosting or your cloud.
How we work
Before any design work, we settle who uses the system, which services it connects to and what happens when one of them fails. That leaves less to redo later.
Payments, logins and integrations have automated tests that run before every release. After launch, error tracking and alerts show us when an API call fails or a page slows down.
The code, the hosting accounts, the domains and the documentation are yours from day one. You can move the work to your own team at any point.
Engagement models
From a company website to a platform you develop for years. Every model starts with a written scope and estimate.
Site or product MVP
Pricing model Fixed scope
Recommended
Portals and integrations
Pricing model Milestones
Scale and compliance
Pricing model Retainer
| Not sure which fits? Describe your users and the systems you need to connect, and we will recommend a model. | Launch | Grow | Enterprise |
|---|---|---|---|
| Responsive, accessible interface | Included | Included | Included |
| Any language, framework or CMS | Included | Included | Included |
| Payments, ERP/CRM and third-party APIs | Not included | Included | Included |
| SEO, performance and monitoring | Included | Included | Included |
| Work across several teams, with architecture reviews | Not included | Not included | Included |
| SLA, security reviews, and long-term support | Not included | Not included | Included |
Technology
A sample of what we work with. We choose the stack per project and are not tied to one.
Questions
What clients usually ask before a web project starts.
The build, the hosting and the support after launch come from one company, so one team answers for the whole project. The code and documentation are written so your own team can take over whenever you choose.
Yes, whatever it is built with. We start with a code review, report in writing what we find and propose a staged plan in place of a rewrite. We can begin with one critical part, such as payments or the API.
Yes. We design REST or GraphQL APIs with token or OAuth 2.0 authentication, versioned endpoints so existing clients keep working after changes, and OpenAPI documentation your partners can integrate from without a call. Webhooks notify other systems when data changes, with signed payloads and automatic retries.
On PN Scripts Hosting, which is hosting from the same company, or on your own cloud. Either way we set up deployment, backups, background jobs and monitoring, and leave written instructions for whoever runs it.
You do. The code, the repositories and the hosting and domain accounts are in your name from day one, and under the contract the intellectual property is yours.
A small first version can go live within a few weeks. Larger portals are built in milestones with a working demo every two to three weeks, and the written estimate gives you the timeline before anything is agreed.
By scope, in one of three models: a fixed price for company websites and first versions, milestone payments for portals and integrations, and a monthly retainer for platforms we develop long term. You get a written scope and estimate, and nothing starts until you have read it and said yes.
Through a working demo every two to three weeks and a shared plan that shows what is done, what comes next and what is waiting on a decision from you.
Yes, if the other system offers an API, webhooks or a data export. Typical connections are payment providers such as Stripe, PayPal or a bank's virtual POS, booking systems, ERP and CRM. Each one gets automated tests, error alerts and documentation, so your team can look after it.
Start
Tell us who will use it and what it connects to
A new build, an API to connect, or code someone else started? Describe it in a few lines and we reply within one business day.
Describe your project