Capabilities
Three kinds of systems, organized around the buyer’s job — not product names. Each family below identifies the closest current evidence on the Work page and its status — deployed, delivered, live, demonstration, or reference design.
Engagements are fixed-scope or T&M, sized to the program’s budget. Ownership, hosting, and handover responsibilities are stated in the SOW; clients retain their data, and custom builds are designed for documented portability rather than hidden lock-in. Work is civilian and unclassified, with accessibility requirements and testing incorporated into delivery. When an existing platform already fits, we say so — the pitch is the workflow, not a license.
Program portals & workflows
What it solves: residents can’t reach services, staff re-key the same forms, and nobody can see where a case stands.
- Typical outputs — role-based portals, application and intake flows, referrals, approvals, e-signatures, and integrations with the systems a program already runs.
- Best-fit buyers — Tribal programs and Native nonprofits, city and borough governments, higher-ed programs, community-service agencies.
- Closest current proof — the ASCF applicant portal and staff review workflow (deployed client engagement, in production) and OlenHub (live OlenArc-operated platform; its cross-agency intake is a demonstration flow).
Assessment, reporting & evidence systems
What it solves: the program’s own logic — competencies, scoring rules, evidence requirements — lives across spreadsheets that become difficult to govern, review, and report from.
- Typical outputs — program-specific assessments, scoring logic, evidence tracking, reviewer workflows, and the reporting outputs accreditors and funders actually require.
- Best-fit buyers — higher-ed and workforce programs, health and training programs, foundations with reporting obligations.
- Closest current proof — the AI-summarized impact reporting layer inside the ASCF platform (deployed client engagement). The deployed proof today covers reporting and evidence outputs; OlenArc does not yet claim a deployed client assessment-tracking system. A working assessment & competency tracking prototype (fictional data, not deployed) shows evaluator scoring, EPA progression, and calibration; an interactive audit-readiness reference design shows the fuller evidence-and-reporting workflow set on fictional data.
Grant operations & dashboards
What it solves: a grant cycle scattered across email, spreadsheets, and a generic national platform that doesn’t match how the program actually works.
- Typical outputs — applicant portals, review queues, e-signed awards, post-award reporting, budget and impact dashboards, and audit-evidence organization.
- Best-fit buyers — foundations, Tribal grantmakers, agencies that administer grant or subaward programs.
- Closest current proof — the full-lifecycle ASCF grant platform across all 8 North Slope Iñupiat villages (deployed client engagement, in production, ongoing); Document-to-Dashboard is a reference design, unbuilt.
Requirements-led, iterative delivery
We agree on the workflow, data, acceptance criteria, decision rights, and delivery boundaries first. Then we put working software in front of the team early, review it regularly, and document any change before it enters scope.
- 1 · Workflow discovery — remote or on-site, by scope.
- 2 · Approved workflow and data map with acceptance criteria.
- 3 · Working prototype in about one week, aimed at the workflow that hurts most.
- 4 · Review against requirements — a usable baseline in about two weeks for a bounded workflow with clear data and decision rights.
- 5 · Documented decisions and change control — integrations, migration, security review, accessibility testing, and rollout are scheduled separately where required.
- 6 · Launch, train, and operate — founder-led through acceptance and ongoing support.
Match a family to your program
Tell us the workflow and where it hurts — we’ll point at the closest deployed proof and say plainly whether we’re a fit.