Sklful Fieldwork
Colour mode
Ours · contrast-verified
sklful-fieldwork sklful-dossier sklful sklful-ink sklful-slate sklful-civic sklful-contrastSklful Technologies, LLC
We help agencies and their prime contractors modernize legacy applications, records workflows, identity, and data platforms. Start with one bounded assessment, then plan the next increment around your operational needs.
For procurement teams: download our capability statement (PDF).
Past performance
Selected work delivered by our principals in previous roles, rather than contracts held by Sklful Technologies, LLC.
Our principal's platform engineering work covered identity federation across 27 agency tenants, an operations portal, and monitoring across 25 cloud accounts. The work reduced the outstanding vulnerability backlog to zero.
Relevant to: multi-agency access and platform operations.
More than fifteen ETL sources consolidated and served to multiple consumer teams over REST and GraphQL.
Relevant to: consolidating legacy data and serving downstream teams.
Over 25,000 documents and 6,695 legacy source files analysed for a COBOL claims-system modernization, with an emulator of the legacy validation logic behind 158 tests so modernized components were checked against what the old system did rather than what its specification said. Each generated citation was mechanically checked against its source before review.
Relevant to: characterizing legacy behaviour before replacing it, and auditing AI-assisted work.
A regulated lifecycle-tracking suite for national laboratories, rewritten off Oracle Forms onto a modern web stack.
Regulated lifecycle tracking
How to start
Start with a fixed-scope modernization assessment of one application or workflow. You keep the findings and can use them with your existing team or a delivery partner.
First engagement
One application or workflow, available documentation, and the people who know how it operates.
The workflow, business rules, integrations, access constraints, and known risks within the agreed boundary.
A system map, business-rule inventory, risk register, modernization sequence, and first increment with acceptance criteria.
Whether to retain, configure, or build—and what a safe first implementation step would require.
The written proposal confirms access, interviews, delivery lead, fixed fee, schedule, and review milestones. The assessment ends with the agreed deliverables and a findings walkthrough; implementation is scoped separately.
Illustrative outline, adapted to the agreed workflow
A separately scoped path through the workflow in a non-production environment, using approved test data. Agree the user task, integrations, and acceptance checks before implementation.
Bring us a defined modernization, identity, or data work package. We will confirm technical fit, staffing, delivery boundaries, and how our work fits your team's processes.
Discuss subcontract supportA bounded engagement may be suitable for simplified acquisition procedures. Your contracting office determines eligibility, the acquisition route, and competition requirements. FAR 13.104 addresses competition.
What we build
Scope the work around the system you need to improve, including its data, access controls, and operating environment.
Intake, lifecycle, disposition, and public-facing status for regulated workflows — citations, permits, filings, licences, inspections.
Oracle Forms, COBOL, and mainframe-era workflows moved to modern web applications with their business rules documented on the way out.
Extraction workflows with validation and human review of exceptions. The interactive example illustrates the routing pattern; accuracy must be evaluated against your documents.
SSO federation over SAML and OIDC, MFA, role-based access, and NIST 800-63B controls across multi-tenant estates.
AWS, Terraform, Kubernetes, and monitoring defined as code, so the environment is reproducible rather than remembered.
ETL from many sources into PostgreSQL and Redshift, exposed to consumer teams over REST and GraphQL.
The assessment compares retaining your system, configuring a commercial platform, and building a custom increment. We weigh workflow fit, integrations, data portability, licensing costs, security requirements, and the team that will maintain it. Custom development makes sense when those requirements justify its delivery and maintenance cost; the recommendation should explain why.
Delivery team
Each proposal identifies the delivery lead by name, any additional specialists, their availability, and how decisions and acceptance will be handled. We name people where the naming is consented and in context — in a proposal — rather than on a public page.
Engineering
Platform and application engineering on federal AI and health-data programs. Author of djust and of the pipeline harness described here.
Confirmed in the proposal
We name proposed data, product, and delivery contributors only after confirming their role and availability for the engagement.
Delivery approach
Agree deliverables, dependencies, acceptance checks, and a fixed price for each bounded increment. Review changes to scope before proceeding.
Review, automated tests, and security checks are stages in our delivery workflow. AI-assisted changes carry the same review responsibility as other code.
Include source code, setup instructions, and a walkthrough in the delivery scope. Agree ongoing support separately, so ownership and responsibilities are clear.
Our open-source workflow and Django-based framework support this approach. Access approvals, security review, validation, and staff training remain explicit dependencies in the plan.
Review the engineering approach and evidenceInteractive example
This synthetic queue shows a low-confidence document held for review. Select Verify to see the record and audit trail change.
Simulated issue: generator signature — held for review.
Interactive workflow simulation. Documents, confidence scores, and automatic reviewer actions are simulated; no OCR or real agency data is used. Select Verify to simulate a review. The 88% threshold illustrates routing, not measured accuracy.
Contact
Email us with the system or workflow, the problem you need to solve, and your desired timing. For subcontract work, include the work package and the skills you need.
The first conversation establishes fit and constraints. If the work fits, we follow with a written scope, fixed fee, delivery team, and schedule for your review.