Services · Primanza LLC
Custom software development, with automation and integration as the specialism.
One service, delivered end to end, and four areas where most of the work falls. Each area below says what gets built and what you hold at handover.
What end-to-end delivery includes
The same six stages on every project, each ending in a deliverable.
- 1.0
- Discovery
- A written understanding of the problem, the current workflow, the systems involved, constraints and the desired outcome.
- 2.0
- Scope and proposal
- Deliverables, assumptions, dependencies, acceptance criteria, timeline and commercial terms, in writing.
- 3.0
- Design and development
- Working software, demonstrated at the points agreed in the proposal, with progress updates at the agreed cadence.
- 4.0
- Testing and acceptance
- The agreed workflows and requirements validated against the acceptance criteria.
- 5.0
- Launch and handover
- The system deployed; the documentation, access and knowledge transfer named in the proposal completed.
- 6.0
- Ongoing support
- Whatever the proposal agreed for this project: scope, duration and cost. There is no standing package.
Custom software development
Software specified, designed, built, tested and deployed to a written set of requirements: web applications, back-office systems, services and the integrations between them.
Typical situations
- A process or product the business runs that no packaged software fits.
- A system that has to be replaced because the vendor is gone or the spreadsheet cannot grow.
- A product idea that needs a working first version, built to be maintained.
What gets built
The full system: data model, application, integrations, deployment, documentation. Technology is chosen for the problem and the people who will run it; recent work is built on TypeScript, Next.js and PostgreSQL.
Business process automation
A process that runs on email, spreadsheets and memory, rebuilt as software with states, rules, owners and an audit trail.
Typical situations
- Approvals, onboarding, quoting or compliance records tracked by hand.
- Work that depends on one person remembering the next step.
- Exceptions that nobody sees until a customer calls.
What gets built
The process as a system: each step with its owner and deadline, validation at entry, automatic routing, notifications, and exceptions sent to a person with the context attached.
Workflow automation
Recurring steps between tools — intake, routing, notification, scheduled work — automated with monitoring, retries and a record of what ran.
Typical situations
- A nightly export someone runs by hand.
- Data that has to be moved from a form, an inbox or a file into a system.
- Notifications and reminders sent from memory.
What gets built
Scheduled and event-driven jobs with logging, retries and alerts, deployed where they can be seen; where an automation platform is the right tool it is used with the same discipline.
API and systems integration
Two or more systems connected through their APIs or files, with a defined source of truth for each field and a log of every record that moved.
Typical situations
- Orders, customers or invoices re-keyed between systems.
- Three tools holding three versions of the same record.
- A vendor API that has to be connected to a system that was never built for it.
What gets built
Integration services that map, validate and move data on a schedule or on events, with idempotent writes, retries and a reconciliation report; webhooks where the systems offer them.
Custom web applications and internal tools
Browser applications for staff or customers: accounts and roles, forms with validation, tables, documents and reports, built around the real workflow.
Typical situations
- A shared spreadsheet that has become a system of record.
- A customer portal for documents, requests or status that nothing off the shelf provides.
- An operations console that has to show several systems at once.
What gets built
A web application with authentication, roles, validated forms, search, history and exports, hosted and documented; accessible by default and usable on a phone.
Who we work with
- Businesses
- Companies commissioning software for their own operations: a problem, a budget, a person who owns the outcome.
- Agencies, software companies and consultancies
- Firms that keep the client relationship and hand Primanza the whole project under the scope they agree with their client. How partnerships work
- White-label partners
- Partners whose delivery is presented under their own brand, where that is agreed in writing. How partnerships work
Technology
Chosen per project for the problem and for whoever will run the system afterwards. Recent work is built on TypeScript, Next.js, React and PostgreSQL, with Stripe where billing is part of the system and OpenAI where language is; the same stack is a sensible default for most web applications and integrations, and it is not forced on a project that needs something else.
Discuss your project.
Describe the problem, the systems involved and what a good outcome looks like. A reply comes within two business days, Monday to Friday.
- Or write to
- hello@primanza.com