Primanza is a software company.
We engineer software for organizations.
We develop software of our own.
Engineering for organizations.
From the first conversation to a running system: requirements, design, build, testing, deployment and handover. Business automation and systems integration are the specialism.
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.
What you hold at handover
A working system accepted against the proposal's criteria, deployed, with its documentation, access and knowledge transfer completed.
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.
What you hold at handover
The process running in a system, with the rules written down and a record of every case.
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.
What you hold at handover
Jobs you can see running, with alerts when something fails and a runbook for when it does.
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.
What you hold at handover
A synchronisation you can audit: what moved, when, and what did not.
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.
What you hold at handover
An application your team can run on, with its hosting, documentation and access handed over.
Six stages, each ending in something you can hold.
The same model on every project. Choose a stage to see what Primanza does, what you do and what it ends in. Timeline, acceptance criteria and commercial terms are decided in the proposal, per project.
What you hold at the end of each stage
Discovery
Understand the problem, the current workflow, the existing systems, the constraints and the desired outcome.
- Primanza
- Asks the questions, maps the workflow and the systems, identifies the data and the people involved, and writes it up.
- You
- Walk through how the work runs today, name the systems and the people, say what a good outcome is.
Ends inA written understanding of the problem, which the proposal is built on.
Scope and proposal
Put the project in writing so both sides can point to it during the work and at acceptance.
- Primanza
- Writes the deliverables, assumptions, dependencies, acceptance criteria, timeline and commercial terms; proposes the cadence of updates and demonstrations.
- You
- Review, question, change and accept the proposal; name who decides on your side.
Ends inA signed proposal.
Design and development
Build the system to the proposal, showing progress as working software.
- Primanza
- Designs the data model and the interfaces, builds, integrates, writes tests, deploys to a staging environment, and demonstrates at the agreed points.
- You
- Attend the demonstrations, answer questions as they come up, provide access to the systems being integrated, give feedback against the proposal.
Ends inWorking software covering the agreed deliverables, demonstrated.
Testing and acceptance
Validate the agreed workflows and requirements against the acceptance criteria.
- Primanza
- Runs the tests, prepares the acceptance walkthrough, fixes what fails, documents what was verified.
- You
- Run the agreed workflows yourself, with your data, and sign off against the criteria.
Ends inAcceptance recorded against each criterion.
Launch and handover
Deploy the system and complete the handover the proposal named.
- Primanza
- Deploys to production, completes the documentation, transfers access and credentials, runs the knowledge-transfer sessions.
- You
- Receive the access, the documentation and the sessions; confirm that the handover list is complete.
Ends inThe system in production, with documentation, access and knowledge transfer handed over.
Ongoing support
Keep the system running after handover, where that is agreed.
- Primanza
- Provides whatever support the proposal agreed for this project: scope, duration and cost.
- You
- Report issues through the agreed channel; decide on changes.
Ends inThe support arrangement in the proposal. There is no standing package or service level outside it.
An independent software company.
Primanza LLC develops software of its own and provides software engineering to businesses. It was organised in Wyoming in June 2026.
Its specialism is business automation and systems integration.
Scope in writing
Deliverables, acceptance criteria, timeline and terms are written in the proposal before work begins, and changes go back to it.
Working software, shown
Progress is demonstrated as running software at agreed points, not described in status reports.
Built to be run
A system is finished when it is tested, documented, deployed and handed over with the access and knowledge its owner needs to operate it.
One accountable person.
The company is run by its founder, who holds the discovery conversation, writes the proposal, builds the system and hands it over: one accountable person from the first conversation to acceptance.
Oğuzhan Enes Önal, Founder & Chief Executive Officer · LinkedIn
Verify the company
Primanza LLC is registered with the Wyoming Secretary of State. The legal notice sets out its legal form, registered agent and address of record.
- Company
- Primanza LLC
- Form
- Wyoming limited liability company, member-managed
- Organised
- June 29, 2026
- Operation
- Operates online; no physical office
Discuss your project.
Describe the problem, the systems involved and what a good outcome looks like. The discovery conversation starts from there, and the proposal puts the scope in writing.
You write
Through the form or to hello@primanza.com: the problem, the systems involved, what a good outcome looks like, and any constraints you already know.
We talk
A discovery conversation about the workflow as it runs today and the outcome you need. A reply comes within two business days, Monday to Friday.
The proposal
Deliverables, assumptions, dependencies, acceptance criteria, timeline and commercial terms, in writing, for you to accept or change.