Skip to content
PN Scripts

PN Scripts · Web development

Custom 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.

Stack
Any language, framework or CMS
Reviews
Working demo every two to three weeks
Ownership
Code, accounts and docs in your name

The standard

Web applications built to be extended after launch

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.

  1. A written scope and estimate before anything is agreed, including what stays out.
  2. Customer portals, marketplaces and internal tools where everyone sees only what they should.
  3. Page speed and search visibility planned from the first template.
  4. APIs with authentication, versioning and OpenAPI docs that partners and mobile apps can rely on.
  5. Build, hosting and support from one company, or deployment to the cloud you already use.
Discuss your project

What we build

Web applications, APIs and integrations

Six areas of work, from a new customer portal to taking over code another team wrote.

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.

  • Roles and permissions
  • Access rules
  • Admin panels

APIs and integrations

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.

  • REST and GraphQL
  • Webhooks
  • ERP and CRM

Performance and SEO

Fast loading, clean markup and structured data that search engines understand, from the first template. Error tracking and uptime monitoring are live before launch.

  • Performance
  • SEO
  • Monitoring

Existing codebases

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.

  • Audits
  • Upgrades
  • Refactoring

Design systems

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.

  • Tailwind CSS
  • Components
  • Accessibility

Hosting and DevOps

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.

  • Background jobs
  • Backups
  • Documentation

The request

How a request travels through your system

We design, build and hand over every layer below.

  1. 01 · Browser

    Interface

    Responsive, accessible screens in the front-end technology that fits, fast from the first visit.

  2. 02 · Any back end

    Application

    Authentication and business rules decide what each user is allowed to see and do.

  3. 03 · Third-party APIs

    Integrations

    Payments, bookings, ERP and CRM connect through versioned APIs and signed webhooks, with retries when the other side is down.

  4. 04 · Background work

    Background jobs

    Slow tasks run in the background, so pages stay fast during traffic peaks.

  5. 05 · Storage

    Data

    A database structure planned for the next feature, not just this one.

  6. 06 · Hosting

    Operations

    Deployment, backups, monitoring and alerts on PN Scripts Hosting or your cloud.

How we work

How we plan, test and hand over

  1. Requirements before design

    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.

  2. Tested before release, monitored after

    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.

  3. Everything in your name

    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

Engagement models

From a company website to a platform you develop for years. Every model starts with a written scope and estimate.

  1. Launch

    Site or product MVP

    Pricing model Fixed scope

    Scope
    MVP or marketing site
    Stack
    Best fit for the project
    Integrations
    Forms, analytics, email
    Support
    Handover with docs
    Request an estimate
  2. Enterprise

    Scale and compliance

    Pricing model Retainer

    Scope
    Platform growth
    Stack
    Full stack
    Integrations
    Many systems, webhooks
    Support
    Agreed response times and reviews
    Request an estimate
Engagement models
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

Technologies we build with

A sample of what we work with. We choose the stack per project and are not tied to one.

  • Laravel PHP applications, REST APIs and admin panels
  • Go Fast APIs and background services
  • Livewire · React Interfaces and dashboards
  • Tailwind CSS Design systems and components
  • MySQL Relational data
  • PN Scripts Hosting Deploys, backups, and SSL

Questions

Questions about custom web development

What clients usually ask before a web project starts.

Why work with PN Scripts?

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.

Can you take over a site or app another team built?

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.

Can you build an API for our mobile app or partners?

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.

Where will the project be hosted?

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.

Who owns the intellectual property?

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.

How long does a web project take?

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.

How is a project priced?

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.

How will we see progress?

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.

Can you connect it to the systems we already use?

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

Ready to plan your project?

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