Frequently asked questions

OlenArc deployed an integrated grant-management platform for the Arctic Slope Community Foundation, serving all 8 North Slope Iñupiat villages.

The ASCF platform covers Anaktuvuk Pass, Atqasuk, Kaktovik, Nuiqsut, Point Hope, Point Lay, Utqiaġvik, and Wainwright. It includes an applicant portal with role-based logins (so applying organizations can track their submissions over time), an admin and review dashboard for ASCF staff, an AI-summarized impact reporting layer, and a navigator chatbot grounded in a local knowledge base. Same module shape is reusable for Tribal Health Programs, state HHS programs, or foundation-funded implementations elsewhere.

Sources: Arctic Slope Community Foundation case study

OlenArc is a civilian software studio rooted in Utqiaġvik, Alaska, with a growing presence in Scottsdale, Arizona, building software for Iñupiat, Tribal, and Native-serving programs.

The studio’s predecessor, Arcnito, won Alaska’s first AI Pitch Competition in 2025 (Alaska SBDC, supported by AWS and PredictIf) and was featured in Alaska Business magazine. The team has exhibited at the North Slope Borough Health Conference (Utqiaġvik), attended NIHB’s National Tribal Health Conference (Chandler, AZ), and was a first-time vendor at the 2026 Reservation Economic Summit (Caesars Palace, Las Vegas).

Sources: About OlenArc · Alaska Business feature · AKSBDC press release

We don’t publish standardized dollar ranges — each engagement is priced to the program’s budget and the module shape.

You can choose fixed-price or T&M for a bounded module. Capture-phase research and prototype work fits under smaller procurement thresholds (including the $10K federal micro-purchase threshold when a prime is using card-swipe procurement — see the Federal teaming FAQ for federal-specific detail). Tell us the scope and the budget on the first call and we’ll give you a price band before any commitment.

See also: Services › Module shapes & engagement shape

About 2–3 weeks for a standard white-label re-deployment of an existing platform pattern.

OlenArc’s OlenHub re-deployment shape: week 1 discovery, SOW co-draft, and brand/content; week 2 local knowledge-base ingest and light partner-agency integration; week 3 pilot launch and handoff inside the client’s repository, cloud account, and documentation.

A deployment that adds healthcare / clinical integrations or new partner-agency referral flows takes longer. A pure re-skin with no new functionality can land in about a week.

Sources: OlenHub case study

Five reusable module shapes: portals, dashboards, AI-assisted document review, intake / workflow systems, and integrations.

A single engagement can span several — the Arctic Slope Community Foundation platform spans four of the five. The three service lines each compose from these same building blocks; the full descriptions, NAICS codes, and a side-by-side of how we’re shaped against typical SaaS and consulting live on the Services page.

See also: Services › Module shapes · deployed examples in Work

A working prototype in about a week; a focused build delivered in a few weeks.

For program leads with a small bounded scope: we get to a working prototype in about a week, then deliver a focused build in a few weeks (larger, multi-part programs run longer). A capture-phase research + clickable-prototype engagement can be sized to fit common procurement thresholds, including the $10K federal micro-purchase. Anything smaller than a focused build we’re probably not the right fit for — we’ll say so on the first call rather than waste your time, and can usually recommend a partner better matched to micro-scopes.

Sources: Capabilities › Module shapes

A working prototype in about a week, then a usable build in weeks, not months — run agile, with a real demo every week. Larger, multi-part programs run longer.

You get a fit / no-fit read within two business days of reaching out, then we co-draft the SOW (in your language for a direct engagement, or your prime’s for a sub-PO). The middle of that window is a tight weekly build loop — prototype, demo, iterate — and it ends with handoff inside your own repository, cloud account, and documentation. An optional sustain retainer or a clean sunset is your call.

See the full six-step flow and sprint timeline on Services › How an engagement runs