Selected clients
COLORADO OFFICE OF THE
ALTERNATE DEFENSE COUNSEL
CENTRAL CALIFORNIA RURAL
REGIONAL ENERGY NETWORK
CITY OF
PHILADELPHIA
SAINT LOUIS
UNIVERSITY
GROUP TRAVEL ODYSSEY
Four legacy systems consolidated into one
Custom CRM spanning six programs
Six years of continuous delivery
18,000 students served
A client relationship in its eighth year
Buy when you can. Build when it counts.
A commercial product or a configured platform is often the better answer, and when it is, we say so. The decision usually comes down to fit and risk:
Custom is usually the wrong answer when
a commercial platform already does the job, the workflow is ordinary, the data is simple, or the budget can’t support long-term maintenance. Building in those cases adds cost and risk you didn’t need.
Custom becomes the right answer when
the process is mission-specific, the data model is institution-specific, the existing system has become a liability (it works, but it depends on one retiring person and can’t safely be maintained or extended), critical work is scattered across disconnected tools, or forcing a generic platform to fit would cost more than building properly. Then the goal is a documented, maintainable system built to outlast the people who built it.
Modern, secure applications, built to public-sector standards
Cloud-native architecture on AWS
Serverless and managed services (Lambda, API Gateway, RDS PostgreSQL, S3, CloudFront, Cognito, SES), provisioned as Infrastructure as Code with automated CI/CD across development, staging, and production. Scales with demand and avoids the per-user licensing model common to many application platforms.
Microsoft .NET and SQL Server delivery
When your procurement or IT standards specify the Microsoft stack, we build there: C#, ASP.NET Core, SQL Server, and IIS, with commercial component libraries such as Telerik. We design to the mandated stack and confirm compliance requirement by requirement.
Modern, accessible front ends
Responsive React / Next.js applications in TypeScript, built to WCAG 2.1 AA and built for the people who use them daily: clean interfaces that replace slow, dated systems staff have learned to work around.
Data migration, done carefully
Mapping, normalization, cleansing, and tested migrations before any cutover, proven at the scale of hundreds of thousands of documents and decades of historical records.
Integration with the systems you depend on
API and secure file-transfer integrations with state payment and reporting systems, identity providers and single sign-on, payment processors, address validation services, public websites, and the other services your environment already runs on.
Role-based access & authentication
Fine-grained role-based access control with SAML 2.0 and single sign-on support (Amazon Cognito or ASP.NET Core Identity, to fit the stack), plus audit trails logging user actions, changes, timestamps, and IP addresses for accountability and compliance.
Public-facing portals and intake systems
Registration and multi-step applications with save-and-resume, secure document upload with validation and encryption, two-factor authentication, online payment, and the administrative back office behind them: dashboards, search and review workflows, reporting, and content your staff manage without a developer.
An architecture built to outlast its parts
Business rules are kept separate from the surrounding technology, and every third-party integration sits behind its own adapter with a development stand-in, so the system can be built and demonstrated before live credentials exist and services can be swapped later without reworking the application. Builds are containerized, so the same application can run in your AWS account, in Azure, or on your own servers.
The right tool for the timeline
When speed and a fixed price matter more than bespoke architecture, we build on proven low-code platforms (Quickbase, Caspio) and say so up front. We recommend the approach that fits the problem.
The systems we’re asked to build
Custom software is a category; these are the shapes it usually takes. Every example is a named client.
Licensing, permitting, and regulated application systems
Online applications, eligibility review, permit issuance with generated documents, renewals, inspections, and public lookup, covering the full license lifecycle, as we completed for the Southwest Utah Public Health Department’s tobacco retailer licensing program.
Benefits and case management
Paper processes converted to structured digital workflows with role-based access, approval routing, document generation, and reporting, as in our ongoing work for the American Samoa Medicaid Agency.
Contractor, billing, and payment management
Contractor lifecycle systems with rate-based compensation, invoicing, and state payment-system integration, as in the Colorado OADC platform below.
Program CRM and compliance reporting
Multi-program data models, state-ready reporting, and equity and geographic dashboards, as in the CCR REN regional energy CRM below.
Relief, grants, and assistance administration
High-volume, audit-ready application review stood up under pressure, as in Philadelphia’s Small Business Relief Fund and the PHDC Rent Assist rental-assistance program.
Customer, vendor, and staff portal ecosystems
Role-specific portals over one shared data layer, with payments, secure documents, and two-factor authentication, as in the Group Travel Odyssey platform below.
Why institutions choose Watkyn for custom software
More structured than a freelance build. More accountable than rented developers. More focused than a large integrator.
Legacy replacement without institutional amnesia
We work out what the old system actually does, preserve the data and the decisions behind it, and hand back a documented, maintainable successor. The single-person dependency that made the old system a risk ends with the replacement.
Public-sector delivery discipline, built in
Requirements sign-off, change control, stakeholder review, UAT, migration validation, and deployment documentation are part of the engagement from the start, so an audit or a staff transition finds the record already in place.
Senior judgment, right-sized team
The expensive mistakes in custom software are architecture, data model, security, and integration, decisions that are costly to undo. We keep senior people on those decisions, engineers who have delivered regulated banking, health, and government systems, without the layers and overhead of a large integrator.
We’ve done the work the way public institutions require it.
Building software for a state agency, a university, or an accountable enterprise is an engineering problem wrapped in a procurement process, a compliance environment, and a set of stakeholders who have to trust the result. Watkyn has won and delivered work through competitive RFPs, collaborated with the people who hold an institution’s operational knowledge, and delivered under the documentation and change discipline public-sector contracts demand.
In practice, that means
Competitive RFP experience and familiarity with public procurement and contracting
Structured discovery with sign-off on requirements before the build begins
Rigorous documentation, change control, and a clear, auditable record of decisions
Automated security scanning through the whole build on custom software work, with findings fixed as they surface
Secure environments configured to meet data-residency and security requirements
A durable, organized project record (decision records, specifications, playbooks, and runbooks) that outlives any individual, on either side
Long-term support, so the institution is never left dependent on a single person again
The same discipline serves nonprofits, associations, and enterprises whose systems answer to boards, funders, auditors, or regulators. How we run every engagement: our delivery methodology →
What you receive
Every custom build leaves you with more than working software. A typical engagement produces signed-off requirements, system architecture, a data model and data dictionary, an integration plan, a security and access-control design, a migration plan, a test and UAT record, a deployment checklist, training materials, user and admin documentation, and a post-launch support plan: the artifacts that let your team operate, audit, and extend the system long after launch. On formal-contract work, all of it lives in a version-controlled project record alongside the source code, so the project can be replayed years later: why each choice was made, what shipped when, and how the system operates.
Real systems, named clients, current work
State government
Colorado Office of Alternate Defense Counsel (OADC)
Problem:
Four interconnected applications managing a statewide network of contracted attorneys and supporting personnel, all built by one developer over 20+ years, now nearing the end of their maintainable life as that developer prepares to retire.
What we built:
Selected through competitive RFP, a single platform replacing all four: managing the full contractor lifecycle from onboarding through firm and case assignment, billable-activity review, rate-based compensation, invoicing, and payment ordering through Colorado’s CORE system. React / Next.js and PostgreSQL in a secure AWS environment, Cognito authentication (SAML 2.0 ready).
Complexity handled:
Single-developer legacy risk
Complex role-based access control with staff-impersonation support
Secure SFTP integration with the state payment system
WCAG 2.1 AA conformance
A CI/CD pipeline with a static-analysis security gate that fails builds on unresolved findings
Careful migration of decades of contractor, case, billing, and invoice records, roughly 300,000 documents
Scope / status:
4 systems → 1 · ~300,000 documents migrated · in final delivery, go-live targeted October 2026 · multi-year support contracted.
Why it matters:
Replaces decades of single-developer legacy risk with one documented, maintainable statewide contractor-management workflow. See our government delivery record →
Regional government
CCR REN (Central California Rural Regional Energy Network), County of San Luis Obispo
Problem:
A brand-new regional body launched with six energy programs, each at a different stage, each with its own data and state-reporting obligations, and no system to manage any of it.
What we built:
A custom, cloud-native multi-program CRM, built from the ground up: each program gets its own data tables and dashboards within one integrated platform, with both periodic data imports and direct staff entry, state-ready CSV reporting filterable by date and field, and equity/geographic dashboards. Fully serverless AWS (API Gateway, Lambda, RDS PostgreSQL, S3, CloudFront, Cognito, SES, infrastructure-as-code, automated CI/CD).
Complexity handled:
Reconciling six different program data models under one roof
Building admin tooling so non-technical staff can add and configure new programs themselves
Full client control of data, with no per-user licensing
Scope / status:
6 programs in one platform · client-configurable without a developer · engaged July 2025, contracted through December 2027.
Why it matters:
Gave a brand-new regional agency one configurable system instead of six disconnected program tools. See our government delivery record →
Municipal government
City of Philadelphia, Department of Commerce & PIDC
Problem:
Business records siloed across many offices. Then, overnight, an urgent need to administer emergency small-business relief at scale during the pandemic.
What we built:
First “Commerce Central,” a shared platform giving every office one reliable view of the city’s businesses; then, rapidly, an integrated Small Business Relief Fund system on the same platform: multi-stage, role-based application review (eligibility → evaluation → executive committee), real-time dashboards by industry and council district, automated applicant status notifications, and automatic generation of preliminary grant/loan documents routed to PIDC. Delivered on a low-code platform (Quickbase) precisely because speed and reliability mattered more than bespoke architecture in an emergency.
Complexity handled:
Multi-office data consolidation
A high-volume, audit-ready review workflow stood up under public-emergency pressure
Document automation into a partner agency’s disbursement process
Scope / status:
Multi-office platform + emergency relief administration · delivered continuously across six years, 2020–2026.
Why it matters:
Helped the city administer emergency relief quickly and accountably under intense public-pressure conditions. Read the Philadelphia case study →
This work was performed for The City of Philadelphia and its Office of the Director of Commerce.
Higher education
Saint Louis University (SLU)
Problem:
A large urban campus needed fast, reliable infectious-disease reporting and case management during COVID-19, and something that wouldn’t be obsolete once the pandemic passed.
What we built:
Watkyn deployed and customized its own ContactPath platform for SLU’s workflows: tracking outbreaks by team, residence, and class section, and integrating with Missouri’s state infectious-disease system. Students gained simple remote illness and vaccination-record reporting; clinical staff gained case intake, triage, dashboards, and closed-loop communication. As the acute phase passed, Watkyn re-architected the disease and symptom logic into SLU Health Connect, now permanent student-health infrastructure.
Complexity handled:
Customizing a product platform to one institution’s specific workflows
Integrating with a state reporting system
Generalizing a single-disease tool into flexible, multi-disease infrastructure without disrupting the people relying on it
Scope / status:
18,000 students served · COVID tool → permanent health infrastructure · engaged October 2020–April 2024.
Why it matters:
Turned a pandemic response tool into durable, permanent student-health infrastructure. Read the Saint Louis University case study →
Learn about ContactPath →
Commercial / travel
Group Travel Odyssey (Kaleidoscope Adventures)
Problem:
A growing group-travel operator whose critical information lived in spreadsheets on different computers, with data re-entered as many as five times and every process depending on individual staff members.
What we built:
An operations ecosystem developed continuously since 2018: a sales CRM, a vendor-management app, a Trip Manager holding every detail of itineraries for groups as large as 600 people, an HR app, and a customer-facing trip portal where travelers register and pay, connected to the Quickbase back office by custom REST services. Custom software where the customer touches it; a platform back office where the staff works. Role-specific access with two-factor authentication, secure document upload, Stripe payment processing with reconciliation and safeguards against duplicate and lost transactions, and save-and-resume registration.
Complexity handled:
Multiple constituencies (staff, vendors, and travelers) on one shared data layer
payment reconciliation at volume; an architecture that has absorbed more than seven years of business change without a rebuild
Scope / status:
Watkyn’s longest-running client relationship · since 2018, begun with predecessor Kaleidoscope Adventures · ongoing.
Why it matters:
an operations backbone the client credits with 12% revenue growth, still expanding in its eighth year. More commercial work: small and midsize business →
The same discipline, on every build
Every engagement above ran on one delivery methodology: structured discovery and requirements sign-off, design and architecture, build and integration, testing and validation, deployment and training, and ongoing support. Today, the build itself runs in a lean, continuous flow with formal phase gates: working software on a steady cadence, a short written status update on the same rhythm, and a documented acceptance point closing each phase, with your sign-off wherever the call is yours to make. It’s the discipline that lets us replace systems without losing data, document work so it withstands scrutiny, and stay engaged for years after launch.
One more test applies before we call anything delivered: the people who depend on the system are trained, comfortable, and using it daily. Until then, the work isn’t done.
1
Discovery
2
Design
3
Build
4
Test
5
Deploy
6
Support
Built for environments where security and accountability are non-negotiable
Access control, data protection, audit logging, and secure integration are designed in from the start, because the institutions we build for operate under real scrutiny. Automated security scanning runs on every custom software build, and on our most security-sensitive government work the delivery pipeline fails a build on unresolved findings.
Some custom builds aren’t departmental tools. They’re ERP-grade operational systems.
We’ve built one: for Nexira, the U.S. sales-and-distribution arm of a global natural-ingredients company, we designed and built a complete operational ERP replacing a legacy Microsoft Dynamics GP (Great Plains) system, covering sales orders, multi-warehouse inventory, invoicing, payment terms, document generation, and reporting, delivered on Quickbase and supported since 2021. That same foundation of legacy replacement, data migration, integration, role-based access, reporting, and long-term support is what our ERP practice is built on.
Questions evaluators ask about custom software
It depends on scope, data migration, integrations, security requirements, and the level of ongoing support, so we don’t quote custom builds from a short form or a single call. That’s how projects go wrong. We start by understanding the current system, the workflow, the data, and the risks, then define a scope and a delivery plan you can evaluate. For smaller or faster needs, we’ll often recommend a fixed-price Quickbase or Caspio build instead of a custom stack.
No. AWS cloud-native is our default for new custom builds, and we also work in client-mandated environments, including the Microsoft stack: C#, ASP.NET Core, SQL Server, and IIS. Because our builds are containerized and defined as Infrastructure as Code, we design deployments to run where your policy requires, whether that’s your AWS account, Azure, or your own servers. When speed and a fixed price matter more than bespoke architecture, we build on Quickbase or Caspio instead. We recommend the approach that fits the problem.
Yes. It’s some of the work we know best. We work closely with the people who hold the institutional knowledge (including original developers, where they’re available), map the full scope of what the old system does, migrate the data intact, and deliver a documented successor built to be maintainable.
Yes. We’ve won and delivered public-sector work through competitive procurement, and we’re familiar with the documentation, contracting, and compliance expectations that come with it.
Yes. We can provide company information, project summaries, methodology detail, and security and compliance information, plus references where client approval permits. For formal procurements, we respond through the required RFP or vendor-review process.
You do. Our custom builds run in your environment, under your control, with no per-user licensing lock-in.
We provide ongoing support. Our engagements typically include multi-year support, so the institution is never left dependent on a single person to keep a critical system running. We also keep watching adoption: if a system we built isn’t in daily use, we treat that as a problem to diagnose, whether it’s a training gap, a fit gap, or a missed requirement, rather than a closed ticket.
Through mapping, normalization, cleansing, and tested migrations before any cutover, so decades of records arrive accurately and completely. When a cutover calls for planned downtime, we schedule and communicate it with you in advance, so operations resume on plan.
Tell us what you’re building, or replacing.
A short call to identify the current system, the risk points, the data and migration issues, and whether custom development is actually the right path, or whether something faster and cheaper would serve you better. The fit call is exploratory; if there’s a serious fit, we can turn it into a structured discovery or readiness review.
Prefer to talk? Call 201-644-5251 or book a fit call (opens in a new tab).
