Business Software Platforms
Design and build custom web platforms for companies that need operational workflows, users, roles, data, reporting, and reliable foundations.
- SaaS foundations
- Internal tools
- Admin workflows
- Business rules
Founder-led software systems practice
Custom software systems for businesses that need the work to actually run.
Petricevic Systems builds B2B platforms, internal tools, data workflows, APIs, integrations, and deployment-ready software foundations. Backend and database engineering are the core strength, but the outcome is a complete working system.
What we build
Business software, not just code delivery.
The work starts with how the business operates, then moves into architecture, data, interfaces, infrastructure, and documentation.
Backend Systems & APIs
Create service layers that are clear to extend: API contracts, authentication, validation, domain boundaries, integrations, and testing.
- REST APIs
- Auth systems
- Third-party integrations
- Service architecture
Data & Reporting Workflows
Model relational databases around real business operations, then expose the data through workflows, dashboards, exports, and reporting paths.
- PostgreSQL
- PostGIS
- MySQL
- Operational reporting
Modernization & Delivery
Replace brittle legacy workflows, organize project structure, containerize development, document decisions, and prepare systems for deployment.
- Docker
- CI/CD structure
- Technical documentation
- Deployment planning
Why this works for B2B
Small enough to stay sharp. Structured enough to handle serious systems.
Business-first scope
Requirements are translated into workflows, roles, data states, and delivery milestones before implementation hardens.
Architecture that can be handed off
Systems are built with clear boundaries, documented decisions, and local development that another engineer can understand.
Practical production thinking
Deployment, logs, configuration, health checks, and maintainability are considered from the beginning.
Engagements
Three practical ways to work together.
The shape depends on what already exists: a new system to build, an old one to repair, or a business idea that needs technical structure before money is spent on implementation.
System Build
For businesses that need a new SaaS platform, internal system, admin portal, API-backed product, or data-heavy operational tool.
- Discovery and scope
- Architecture and data model
- Implementation
- Deployment preparation
Modernization Sprint
For teams with brittle workflows, unclear backend structure, database pain, missing documentation, or deployment friction.
- Technical audit
- Refactoring plan
- Targeted implementation
- Handoff documentation
Architecture Partner
For founders and operators who need technical direction before committing budget to a larger software project.
- Domain modeling
- API and database design
- Risk review
- Build roadmap
Selected work
Systems with private code, public architecture-level context.
Some projects are proprietäry or client-owned, so public descriptions stay focused on engineering scope and system responsibilities.
IMSMA-BHMAC
A data-intensive information system designed to replace legacy Paradox-based infrastructure used for mine action operations and geospatial workflows.
- Modeled minefields, surveys, clearance workflows, and reporting concepts.
- Built backend services with Go, PostgreSQL, and PostGIS.
- Defined service contracts with Protocol Buffers.
- Implemented JWT access and refresh-token authentication with bcrypt password handling.
KonektorHub
A SaaS platform for CNC and metalworking businesses managing partners, invoices, payments, inventory, expenses, reports, and day-to-day operations.
- Designed tenant isolation and business-domain boundaries.
- Structured backend services around hexagonal architecture.
- Organized a monorepo with web, API, and shared packages.
- Prepared local development and delivery workflows with Docker Compose.
Client Applications
Client-focused application work across mobile platforms, REST integrations, authentication, chat, ticketing, local storage, and support workflows.
- Delivered iOS and Android application features.
- Integrated Firebase-backed workflows and REST APIs.
- Worked with Core Data and Realm local storage.
- Implemented customer support and ticket-based messaging flows.
Delivery process
A clear path from messy workflow to working system.
01 Clarify the business workflow and define the real operating problem.
02 Model the domain, data, users, permissions, and system boundaries.
03 Design the API, database schema, integration points, and deployment approach.
04 Build the system with maintainable modules, validation, testing, and documentation.
05 Prepare the project for production operation, handoff, monitoring, and future growth.
Fit
Clear fit beats vague capability lists.
Petricevic Systems is best suited for businesses that need a maintainable software system behind the operation, not just a nice-looking page.
Good fit
- B2B companies replacing spreadsheets, paper, or fragile internal tools.
- Founders who need a practical first version of a software platform.
- Teams with backend, database, integration, or reporting problems.
- Businesses that value maintainability, documentation, and clear ownership.
Not the right fit
- Pure landing pages with no software system behind them.
- Projects that only need visual branding or social media design.
- Throwaway prototypes with no concern for data, security, or future maintenance.
- Work where technical decisions cannot be discussed honestly.
Trust layer
Professional enough to protect the work, lean enough to keep ownership close.
01Source code and client-specific business logic remain private by default.
02Architecture decisions are documented so the system can be maintained later.
03Local development is designed to be understandable and repeatable.
04Scope is shaped around useful releases, not vague open-ended effort.
05Additional specialists can be brought in when project scope requires it.
Start with the system