software
ARP is a framework — and the team that builds on it. The four common starting points below are where most projects begin. Where they end up is always different, because every team is.
| type | crm | ats | hrm | cms | custom |
| foundation | php · laravel · filament |
| ai-ready | openai · rag |
| ownership | yours · project-priced |
| hosting | self or arp-managed |
Geometric, lowercase, modest, confident. Manrope picks up the same construction at every size. JetBrains Mono carries the technical labels.
Two families. The sans does the reading. The mono does the labelling — measurements, identifiers, captions.
built to fit.
built to last.
Pick a starting point — a CRM, an HRM, a content system. Toggle features. Watch the dashboard reshape. Then describe the part we haven't listed yet, because that's where every project actually begins.
$ arp init --from=crm --shape=yours
SECTION LABEL · TECHNICAL CAPTION
The wordmark's gray is the body type colour — softer than black, in concert with the mark. Vermillion replaces the previous rose for a punchier, complementary decision colour.
Same component shape language as Wordmark — small radii, soft shadows, generous space. Where decisions live, accent steps in.
Sales & client relationships, shaped around your pipeline.
A pipeline shaped around your sales process. Toggle features. Watch the dashboard reshape. Or describe the part we haven't listed yet.
| defaults | 05 |
| features | 14 |
| custom paths | ∞ |
| avg ship | 6 wks |
| shipped | 12 applications |
| ai-ready | yes |
A three-column feature row, used on the home page to set the brand's argument before the case studies.
We don't sell a CRM with your logo on it. We build a CRM shaped around your sales process — your stages, your fields, your edge cases. Same for an HRM, an ATS, or something with no category at all.
$ read moreEvery ARP project is yours. Project-priced, not subscription. Self-hosted or managed — your choice. No platform lock-in, no surprise pricing tiers, no feature paywalls.
$ read moreFourteen years on one framework means we start at week four, not week zero. The foundation runs in production at forty companies. Your project starts where they ended.
$ read moreThe case-study row from the home page. Each card opens into a full case study with screenshots, numbers, and quotes.
A single registry replacing five disconnected systems. Handles Slovenian labour law, multi-entity org structure, and one custom approval chain per division.
Replaced a 12-year-old internal tool. Two pipelines, B2B portal, document approval, AI inquiry routing into the correct sales region.
Doesn't fit any module name. Equipment registry, work-order routing, contractor approvals, citizen-facing portal. Shipped in three phases over six months.
The process block from the How It Works page. Four numbered stages with a typical timeline.
We sit with your team and map the actual process — not the org chart, the actual one. Output is a scoped brief with feature list, integrations, and a fixed quote.
Information architecture, screens, copy. You see the application before we build it. Approvals happen at the artifact level, not in dev tickets.
We compose on the framework, ship in two-week iterations, and you run the application alongside the team that built it. No handoff to "an account manager."
The application is yours. We stay on as a small retainer for evolution — or you take it in-house. Either way, the code, the data, and the deployment are yours from day one.
For the home page and case study pages. One quote, attributed, no photo necessary.
ARP built the application our team would have built if we'd had the time and the framework. Two months in, no one on payroll remembers using anything else.
Used between case studies and the final CTA on the home page. Light scaffolding, big numbers.
End of every long page. Big statement, two clear actions. No hard sell — we don't have a sales team.
Tell us the part you wish a system did. We'll tell you what we'd build, what it would cost, and how long it would take. No proposal deck.
Small section above the final CTA. No logos — just names, set in mono.