Raken — Competitor Decision Brief

Dashboard: Dashboard · method: _RESEARCH-METHOD · market grid: _MARKET-PROBLEM-MAP · opportunity lens: _OPPORTUNITY-LENS · landscape: competitor-landscape-report

Purpose: decide whether we can enter the part of the market Raken occupies and build a profitable, defensible product. The brief explains what Raken is and how it works, then where its value sits and what users experience, and finally our own opportunity. Evidence (248 analysed reviews, screenshots) is at the end.

Snapshot

Where Raken plays across the market

Scored 0 (not addressed) to 100 (best-in-class) against the 21 areas in _MARKET-PROBLEM-MAP, sorted by coverage.

Takeaway: deep in field capture, time/labour and safety; progressively thinner toward the commercial and financial side. The two areas central to our thesis — turning field evidence into recovered money, and reusing historical cost data — are where Raken is weakest. That is the space we want.

The input side — how work gets captured

• Captured: daily reports (work, weather auto-filled, manpower/labour hours, equipment, materials, notes), photos/video, time cards (clock-in/out), safety and toolbox talks, checklists, observations/incidents, RFIs (Performance tier).
• Input methods: voice-to-text dictation, one-tap photo, structured forms, shared-device kiosk time clock, automatic weather.
• Onboarding / ease: the most-praised aspect; non-technical crews adopt quickly, onboarding is fast and well-supported.
• Friction (from reviews): time-tracking and clock-in draw recurring bug complaints; the app gets unreliable on poor signal. Capture is excellent for reports/photos, weaker for time.

The management side — what the office sees

• Lands in the web dashboard (Insights): manpower/labour trends, safety-incident counts, checklist compliance, QC issues, task/progress across projects, RFI logs with cost/schedule/plan-impact flags. Presented as charts.
• Who consumes: project managers and ops (production + safety), executives (cross-project visibility without site visits), payroll/finance (hours → approval → accounting).
• Valued most: real-time visibility.
• Pain points: limited report/timesheet customisation; analytics seen as shallow or hard to configure; no client-facing portal; brittle integrations (Sage 300, ADP named).
• Structural gap (evidenced): the dashboard is operational only — manpower, safety, productivity, progress. No commercial or margin view, no variation/claim pipeline, no register of missing or at-risk evidence. The office can see how the work is going, not how the money is moving.

Where the value actually comes from

• Do not attack: capture experience, the labour-to-payroll loop, the accounting integrations — entrenched, owned by office/finance, Raken’s strongest ground.
• Where value stops: Raken converts field evidence into operational visibility and payroll. It does not convert it into recovered money (structured variations, delay narratives, entitlement claims), and the dashboard has no commercial view. That boundary is our interest.

What users say — both sides

Credibility first: of 248 analysed reviews, ~66% were vendor-solicited (invited, often incentivised); only ~22% are organic, so discount the ~4.6 average accordingly. The sub-ratings, once unrated (blank) entries are excluded, are high and tightly clustered — ease of use and support 4.69, value for money 4.54, features 4.45 — so the friction is not in the scores. Where pricing shows up is the review text (opaque quote-only pricing, a second-year increase), not a low number.

• Representative positive (COO, civil engineering): cloud access, ease of use, detailed field reports, shareable photos/weather, and the stored record’s value in disputes.
• Signal for us: the recurring “missing change orders” complaint points straight at the commercial gap; and the pricing complaints in the review text — opaque quote-only pricing and a second-year increase, not a low score — say a transparent, lower-cost offer still lands on a real grievance.

The opportunity for AI in this space

• AI does not help Raken’s core. Time-to-payroll is structured data entry and integration plumbing; the value is in the accounting connections, not in anything a language model replaces. Competing there gains nothing.
• AI can take over the commercial layer Raken skips. Change-order narratives, delay/disruption claims, RFI drafting, and turning logs and photos into structured evidence are document-heavy, generative tasks that cheap models now do well. The barrier is no longer build cost (inference is effectively free) but data access and judgement — and Raken already captures the data.

What we would build:

• Baseline to match: reliable field capture (no one adopts a commercial tool that makes daily logging worse).
• Recurring pains we can solve: dependable time tracking, cleaner integrations, and above all the change-order/claims workflow users keep asking for.
• Niche to target first: the commercial and entitlement layer for UK mid-market commercial and fit-out contractors — where Raken is weak on the commercial side and on US-centric fit, and where recovering money from variations and claims is a board-level concern.

How open the platform is

• API / integrations: public REST API 3.0 (OAuth2); connects to Sage, QuickBooks, Viewpoint and other project tools.
• What it means: we can build alongside Raken rather than replace it — an AI layer reads the daily logs and RFIs a contractor already captures and adds the commercial workflow on top, lowering the adoption barrier. The same openness is available to others, so it is no moat for Raken. On balance it favours an entrant: far easier for us to sit on Raken’s data than for Raken to build the commercial product.

Raken’s own AI — claims, shipping, and how far they can go

Raken has shipped real AI, which beats most peers, but the substance is narrow and gated to the top tier.

• All three are polish on the capture side Raken already owns; none touch the commercial layer (no change narratives, delay evidence, or historical-cost benchmarking), and there is no module to hang one on.
• AI sits in the most expensive tier — treated as a reason to upgrade, not something to give away.
• Industry conversation (e.g. Procore’s announced AI agents) is about AI inside the system of record; Raken’s shipped AI is entirely capture/admin. The distance on the commercial side is wide — that is our window.
• Confidence they close the commercial-AI gap themselves within ~2 years: low (about 1 in 4). Reasons: it is a different product with a different buyer; their incentive is to gate AI behind the top tier; their stickiness and roadmap are anchored in payroll/accounting integrations, pulling effort toward operations, not claims. Main risk to this read: acquisition.

Who actually uses Raken

• Roughly three-quarters are under 200 employees; enterprise is ~6%. Satisfaction is flat across sizes, so this is a reach question, not a fit one — Raken sells to smaller contractors because that is who it sells to.
• Role: office ~47% vs field ~31% (the paying decision sits in the office).
• Industry: overwhelmingly general construction, then civil engineering, utilities, electrical.
• Alternatives considered: Procore by far the most common (×12), then SALUS, TimeTrex, QuickBooks Time, BusyBusy.
• Switched from: most often spreadsheets and shared drives; occasionally Procore or Fieldwire. Raken usually wins by digitising a paper/Excel contractor.

Our read — can we enter and win?

Yes, on a specific and defensible basis, provided we stay disciplined about where we compete. Do not attack Raken’s strengths (capture, the payroll loop, accounting integrations, US distribution). Enter on the other side of the product, where it stops: turning field evidence into recovered money. Because the platform is open, the way in is a narrow, inexpensive AI layer that reads logs and RFIs and drafts change-order and delay-claim evidence — priced transparently against Raken’s opaque quote-only motion — then expands into historical-cost benchmarking, the durable, data-compounding part of the thesis.

The app itself — ratings and reception

The small UK count underlines how US-centred the business is. The App Store listing leads on exactly the confirmed strengths: real-time field data, photo/video capture, branded PDF reports, and the shared-device time clock.

Screenshots

Grouped by theme, full-size, scrollable. Images render in Obsidian and exported HTML through embeds (referenced, not copied). Full set and gathering method: screens/README. Two whole-set contact sheets are linked at the end for a quick overview.

The product at a glance — the module map

One screen lists the whole product: daily logs, photos, time cards, production, equipment, materials, toolbox talks, directory, observations, gallery, insights, and the kiosk clock.

Daily reporting — the core workflow

The structured daily log: work performed, weather, hours, notes, attachments, then sign and complete.

Capture — photos, time, safety

One-tap photo and video capture; the time-card entry; the shared-device clock-in kiosk; and the safety / PPE review checklist.

Output — branded PDF reports

The professional, branded report that gets sent to clients, on phone and on tablet.

The office / web side — the dashboard

The web Insights dashboard the office consumes (project rollups and stats) and a web admin view (toolbox talks with weather and reporting controls). This is the side the App Store never shows.

In the field

The app in use on site.

Whole-set contact sheets

For a single-glance overview of everything captured: contact_appstore.jpg (all App Store screens) and contact_video.jpg (all walkthrough-video frames).

Sources and method

• Product / dashboard / tiers / API: vendor site corroborated by search — raw/exa_full_product.json, raw/exa_features_facts.json, raw/exa_api.json, raw/parallel_full_product.json.
• AI claims: Raken newsroom/blog + search — raw/exa_ai_chatter.json, raw/psearch_ai_chatter.json.
• Reviews (real segmentation): 248-review DOM/RSC scrape recovering real company size, role, industry, sub-ratings and solicitation — raw/capterra_dom_corpus.json, rolled up in raw/analysis/SUMMARY_DOM.md.
• App Store ratings: raw/appstore_app_us.json, raw/appstore_app_gb.json. Screenshots and gathering method: screens/README.
• Method, limits, and the discipline of not asserting an absence without evidence: _RESEARCH-METHOD.