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. The same system shape is reusable for Tribal, foundation, and public-program implementations elsewhere.

Sources: Arctic Slope Community Foundation case study

OlenArc is a founder-led custom systems studio founded in Utqiaġvik, Alaska and based in Arizona, building systems for Iñupiat, Tribal, Native-serving, and public 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 can be sized to smaller procurement paths. Tell us the scope and the budget on the first call and we’ll give you a price band before any commitment.

See also: Capabilities

Yes — OlenHub is a live OlenArc-operated platform, configured and operated per community, and the community keeps its data.

It is not licensed as off-the-shelf software. Scope, timeline, pricing, hosting, and operating responsibilities for a community deployment are defined in the proposal or SOW. Work that adds healthcare / clinical integrations or new partner-agency referral flows takes longer and is scheduled accordingly.

Sources: OlenHub case study

Three system families: program portals & workflows; assessment, reporting & evidence systems; and grant operations & dashboards.

A single engagement can span several — the Arctic Slope Community Foundation platform spans portals, intake and workflow, dashboards, and AI-assisted reporting. The three families, with their typical outputs and closest deployed proof, live on the Capabilities page.

See also: Capabilities · 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 smaller procurement paths. 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.

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 acceptance and handover — source-code, repository, cloud-account, hosting, and handover terms are defined in the SOW. An optional sustain retainer or a clean sunset is your call.

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