A glacier and frozen lake under an Arctic sky in Alaska.
Project experience

Deployed work and capability demonstrations

This page is written for evaluators. Every item carries one of five status labels, and the deployed work is named and checkable.

Status key

Five labels, used consistently

  • Deployed client engagement — built for a named client, in production, with real users.
  • Delivered and still live — a completed, closed-out engagement whose system remains in operation.
  • Live OlenArc-operated platform — our own platform, publicly available, operated by us.
  • Demonstration flow — a working flow shown for illustration; production use needs agreements not yet in place.
  • Reference design — an interactive or documented design on fictional data; not built for a client.
A · Deployed and delivered

In production today

Three live bodies of evidence, each with the same evaluator fields: context, what was delivered, current status, responsibility, capability, and evidence.

Grant-management impact dashboard — a map of the North Slope with a circle at each of the eight villages sized by grant dollars awarded (demonstration configuration, fictional sample data).

Illustrative screen This screen uses fictional sample data from the demonstration configuration — the client engagement itself is deployed and in production.

Deployed client engagement · in production · ongoing

Arctic Slope Community Foundation — grant platform

Program context: a regional foundation making grants to organizations across all 8 North Slope Iñupiat villages, previously run on a national commercial grants product that didn’t fit the program.

What was delivered: a full-lifecycle grant system — applicant portal, staff review queue, e-signed awards, guided post-award document collection, grantee progress and final reports, budget tracking, and an AI navigator chatbot with an AI-summarized impact reporting layer.

Current status: in production since 2026, serving applicants across the region — replacing the prior national grants platform. Delivery & operating responsibility: OlenArc built the system and operates it under an ongoing engagement — hosting, support, iteration, and the platform’s budget and impact reporting outputs. Specific reporting and evidence functionality includes review-decision audit trails, e-signed award records, guided post-award document collection with completeness tracking, and staff-reviewed AI-summarized progress reporting. Relevant capability: grant operations & dashboards, program portals & workflows. Evidence: references available for active procurements.

Delivered municipal engagement · calendar still live

City of Utqiaġvik — community calendar

Program context: the northernmost city in the United States (~4,500 residents), where community events were scattered across flyers and Facebook posts with no single calendar.

What was delivered: an AI-aggregated community calendar — the pipeline reads publicly posted flyers and updates, lifts date, time, and place out of the artwork, categorizes each event, and de-duplicates the same event across sources.

Current status: the engagement was delivered, invoiced, and closed; the calendar remains live and refreshes daily. There is no ongoing contract. Delivery responsibility: OlenArc built and delivered the system under a fixed-fee direct municipal engagement — a useful reference for how we hand off cleanly: the pipeline runs without our day-to-day involvement, and the City was never locked into a retainer to keep its calendar alive. Relevant capability: program portals & workflows. Evidence: the live calendar itself; references available for active procurements.

The City of Utqiaġvik community calendar in production — a month view where every day carries events compiled from City, school, Tribal, and community sources, color-coded by category.
OlenHub home screen in production — Today on the North Slope with live weather, Ask Olen online, and the week's events.
Ask Olen — OlenHub's AI guide answering everyday questions from cited local sources.
Live OlenArc-operated platform · App Store · Google Play · web

OlenHub — community platform

Program context: Arctic Slope residents check multiple local pages and posts to find events, services, and safety information — on phones, over weak connections.

What was delivered: a community app for Arctic Slope residents — one aggregated calendar updated twice daily with add-to-calendar and share on every event, Ask Olen (a cited-answer local navigator), an offline Safety Kit that works with no signal, and a weekly community digest.

240 residents reached — ≈2% of the whole North Slope (pop. ~11,000)all 8 North Slope villages386 Utqiaġvik events published106 help-seeking questions askedas of Aug 2026

Current status: live on the Apple App Store, Google Play, and the web; the calendar updates twice daily and the platform is built mobile-first for low-bandwidth conditions. Operating responsibility: OlenArc-owned and operated — content pipeline, moderation, releases, and store publishing are ours; each community deployment is configured with the community, and the community keeps its data. Relevant capability: program portals & workflows. Evidence: the public apps themselves — download and check — and a public usage report with weekly trends, per-village reach, and what residents ask for: olenhub.com/impact.

B · Capability demonstrations

Capability demonstrations

Shown, not sold as deployed. These working demonstrations and reference designs answer a different question than the deployed work above: can we design and build the adjacent workflows a procurement asks for. Every screen runs on fictional data, and none of these is a deployed client system.

Clinical skills tracker concept — program dashboard with encounter counts by setting, cohort progress toward completion targets, and a needs-attention queue (fictional sample data).
Competency progression screen — entrustment levels by EPA per student across terms, domain rollups, and an evidence-linked coaching plan (fictional sample data).
Working prototype · fictional data · not deployed

Assessment & competency tracking

A sanitized health-education concept: evaluator scoring across simulation lab, clinic, and rotation sites; competency (EPA) progression; faculty calibration (weighted κ); accreditation evidence exports.

  • Functional — a clickable multi-screen prototype: navigation, cohort and student views, and sample flows work in the browser; records and exports are illustrative.
  • Demonstrates — program-defined rubrics, versioned competency crosswalks, interrater reliability statistics, and accreditor-facing reporting in one interface.
  • Boundary — a working prototype only, never a client project or past-performance example; summative decisions stay with faculty.
Interactive reference design · fictional data · not deployed

Audit-readiness & reporting workflow

An audit-season workspace for a federally funded program: deadline tracking, auditor (PBC) request handling, a missing-evidence queue, a per-award evidence binder, SEFA tie-out, and staff-reviewed export packets.

  • Functional — the full workspace is clickable in the browser on fictional data, no login. Explore the reference design →
  • Demonstrates — the evidence-organization and reporting workflows we build into custom grant-management systems, informed by the deployed ASCF grant-operations work.
  • Boundary — not a deployed client system; it organizes evidence and does not replace your CPA or auditor.
Audit-readiness workspace — command center tracking blocked auditor requests, missing evidence by owner, readiness by grant, and upcoming deadlines (fictional sample data).
Grant evidence binder — awards with ALN/CFDA, award period, expenditures, evidence completeness, and SEFA tie-out status (fictional sample data).
Navigator assistant answering a resident's question from cited local sources before offering an intake handoff (demonstration).
Cross-agency intake demonstration — a pre-filled partner-agency referral form with signature capture and an explicit data-sharing consent step (fictional data).
Working demonstration flow · fictional data · not in production

Community & health-adjacent intake workflow

A guided intake flow: the navigator pre-fills a partner-agency referral form, captures a signature and an explicit data-sharing consent step, and routes the submission for staff review.

  • Functional — the flow runs end to end inside OlenHub as a demonstration: pre-fill, signature, consent capture, and routing.
  • Demonstrates — consent-first intake, routing, and staff-review patterns for community and health-adjacent programs. No PHI is collected, and OlenArc does not accept PHI by default.
  • Boundary — production use requires partner-agency data-sharing agreements; not part of the deployed ASCF engagement; no healthcare past performance implied.

A further documented-but-unbuilt pipeline design — OCR → AI extraction → dashboard → drafted narrative with human review — is written up as Document-to-Dashboard (reference design · unbuilt).

For evaluators

What you can ask us for

  • References — available for active procurements, in your required format.
  • A live walkthrough — a screen-share of the deployed ASCF system on its demonstration configuration (fictional data), or the public OlenHub apps directly.
  • Delivery artifacts — sample acceptance criteria, workflow and data maps, and change-control records from real engagements, redacted where client confidentiality requires.
  • A scoped response — for an active procurement, we provide a fit/no-fit response within two business days. A working concept may be offered when it is separately scoped and the solicitation or capture arrangement permits it.

Want to check any of this?

References for the deployed work are available for active procurements. Tell us what your evaluation needs and we’ll provide it in your format.

Discuss a program See capabilities
Book a call