Renvik

Renvik

An AbaSoft mobile-first SaaS in active development for field-service companies, connecting customers, quotes and customer acceptance with the wider job-to-invoice workflow.

ABA Soft product

An AbaSoft product in active development. Product architecture and full-stack implementation by Bujar Ademi.

Overview

Renvik is an AbaSoft SaaS product currently in active development for small field-service companies. Its product model connects company setup and customers with quotes, customer responses, jobs, proof of work and invoicing.

The implementation combines a .NET modular monolith with SQL Server persistence, Angular administration and an Angular/Capacitor mobile application. The mobile customer and quote workflows are already implemented; the broader product continues to evolve through phased delivery.

Key features

Company workspaces

Tenant-scoped records and membership roles

Customers and sites

Customer records and service-location management

Quote editing

Guided mobile draft creation with line items and review

Quote revisions

Immutable document revisions and explicit state changes

Customer responses

Public quote access separated from office accounts

Mobile experience

Angular and Capacitor workflows for field use

Case study

Context

Small field-service businesses need to connect customer information, site details and commercial documents with work performed in the field. Renvik is being developed to support that lifecycle from a mobile-first product rather than separate office spreadsheets and disconnected messaging.

My role and ownership

Renvik is an AbaSoft product. I work on product architecture and full-stack implementation across the API, administration experience and mobile application. This is an ongoing development case study, not a claim of a completed public launch.

Implemented foundation

The codebase includes company-based tenancy, membership and role boundaries, customer and service-site management, quote revisions and explicit quote lifecycle operations. The mobile quote module supports searching and filtering, a guided editor, line items, photos, review, document preview and sharing through the supported API contracts.

Technical approach

The backend follows a .NET modular-monolith structure with vertical slices, Mediator, Entity Framework Core and SQL Server. Angular uses NgModules and Zone.js, while Capacitor provides the mobile integration boundary. Commercial calculations and authorization remain server-owned.

Quote changes create immutable revisions. Issued or accepted facts are treated as snapshots rather than silently recalculated from mutable customer records. Company scoping is carried through business records and associations. Public quote access is separated from authenticated administration so a customer can respond without receiving an office account.

Engineering challenges

The main challenge is keeping the customer-facing document, office workflow and mobile editor consistent as quote state changes. Explicit commands, revision boundaries and capability checks make those transitions visible and enforceable. Mobile screens distinguish loading, empty data and actionable failures rather than substituting demonstration records.

Current status

Renvik remains in active development. Customers and quotes form a concrete implemented part of the product; jobs, field evidence, invoicing and subscription capabilities belong to the wider product lifecycle and are developed in controlled phases.