Sklful Technologies, LLC · Knoxville, Tennessee
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.
Principal experience
GSA agency identity · CMS data platforms · regulated records systems
Download capability statement (PDF)Simulated issue: plate number — 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.
Past performance
Selected work delivered by our principals in previous roles, rather than contracts held by Sklful Technologies, LLC.
John Tipton'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 converted in support of a COBOL claims-system modernization. Each generated citation was mechanically checked against its source before review, providing traceable documentation for the modernization effort.
Relevant to: documenting business rules 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
We agree the system boundary, available documentation, permitted access, and stakeholder interviews before quoting. The proposal names the delivery lead, fixed fee, schedule, and review milestones.
Acceptance covers the agreed deliverables and a findings walkthrough. Production changes, full codebase analysis, and implementation are outside the assessment unless explicitly included.
Timing depends on scope, access, and confirmed staffing. We agree a start date and delivery schedule in the proposal.
Discuss an assessmentA 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 homepage simulation 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.
Principals
Engineering, data science, and delivery leadership in one team. Each proposal identifies who will do the work and how decisions and acceptance will be handled.
Engineering
Platform and application engineering on federal AI and health-data programs. Author of djust and of the pipeline harness described here.
Data science
Data science principal, focused on analytics and modelling.
Product & delivery
Product ownership and delivery management — scope, acceptance, and the conversation with your stakeholders.
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 evidenceContact
Email John Tipton 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.