04 / Custom Software

Software shaped around the way your business actually works.

Replace fragile spreadsheets, disconnected plugins, and rigid applications with a purpose-built web, desktop, or mobile system designed around the people and processes that use it.

BEST FOR / BUSINESSES THAT HAVE OUTGROWN SPREADSHEETS, PLUGINS, OR OFF-THE-SHELF SOFTWARE

Discuss your software idea

Purpose-built business systems

Focused software for real operational needs.

The platform and architecture follow the actual users, workflow, constraints, and long-term support needs—not a predetermined technology stack.

01

Internal business applications

Custom systems for workflows, records, approvals, scheduling, inventory, production, service delivery, and other internal operations.

02

Customer and employee portals

Secure applications where authorized users can submit information, review status, exchange documents, manage requests, or access appropriate services.

03

Web applications

Browser-based applications accessible across supported computers and devices without installing traditional desktop software.

04

Desktop applications

Applications for Windows, macOS, or Linux when local access, device integration, offline operation, or another desktop-specific requirement justifies the approach.

05

Mobile applications

Purpose-built mobile experiences for appropriate iOS and Android use cases, with supported platforms, app-store responsibilities, developer-account ownership, and post-launch updates defined in the proposal.

06

Integrations and APIs

Connections between applications, databases, external platforms, and custom services where compatible and permitted access is available.

07

Data migration

Plan, transform, validate, and transfer agreed data from spreadsheets, databases, or previous systems, with quality, exclusions, backups, validation, and approval responsibilities defined in scope.

08

Existing software modernization

Evaluate, stabilize, extend, or replace existing software when the client has the source code and sufficient legal authority to modify it.

09

AI-assisted software

Add appropriate OpenAI or Anthropic capabilities for language, classification, extraction, summarization, drafting, or knowledge retrieval when AI provides meaningful value.

Greykhat can evaluate software originally created by another developer only when the client has lawful access to the source code and the applicable contract or license permits modification.

Greykhat will not alter proprietary software, bypass technical restrictions, or modify copyrighted code when the client does not have the necessary rights or permission.

Greykhat begins with a complimentary, time-limited discovery consultation to understand the business problem, intended users, existing systems, and desired outcome.

A straightforward project may be scoped after that initial conversation. More complex software may require a paid discovery and planning engagement before a complete development proposal can be prepared.

Paid discovery may be appropriate for

  • End-to-end process mapping
  • Multiple user roles or departments
  • Complex business rules
  • Several integrations
  • Data migration
  • Web, desktop, or mobile delivery
  • Security or compliance requirements
  • A phased product roadmap
  • Significant technical research
  • Detailed requirements before accurate pricing is possible

Paid discovery can produce

  • Process and workflow documentation
  • User and role definitions
  • Prioritized requirements
  • Integration and data requirements
  • Technical recommendations
  • Risks and dependencies
  • A phased implementation plan
  • A refined development scope or estimate

From business problem to working software

A visible path from discovery through support.

You work directly with Jessie throughout the engagement—from understanding the process through design, development, testing, explanation, and handoff.

  1. 01

    Initial consultation

    Determine whether Greykhat is a potential fit and whether additional discovery is required.

  2. 02

    Discovery and planning

    Understand the complete process, users, information, systems, constraints, and intended outcome.

  3. 03

    Scope and proposal

    Define deliverables, platforms, responsibilities, schedule, pricing, ownership, and third-party dependencies.

  4. 04

    Product and technical design

    Plan workflows, interfaces, data structures, permissions, integrations, and deployment.

  5. 05

    Development in visible stages

    Build the approved functionality with regular progress reviews.

  6. 06

    Testing

    Test expected workflows, permissions, validation, integrations, supported devices, data migration, and important failure conditions.

  7. 07

    Deployment and migration

    Deploy to the agreed environment and transfer approved data when migration is included.

  8. 08

    Documentation and handoff

    Deliver the agreed source code, documentation, credentials, and operational information.

  9. 09

    Optional ongoing support

    Continue hosting, monitoring, backing up, maintaining, and improving the application under an annual support agreement.

After full payment, client-specific source code and project documentation are delivered to a client-owned repository in accordance with the project agreement.

The agreement identifies

  • Pre-existing Greykhat components
  • Reusable libraries or development tools
  • Open-source software
  • Third-party components
  • Commercially licensed services
  • Client-provided code or content
  • Restrictions that continue after delivery

Client ownership does not include ownership of third-party platforms, open-source projects, or pre-existing Greykhat materials incorporated under their applicable licenses.

Greykhat may retain a private archival copy of the final software deliverable when authorized by the project agreement. This archive is maintained as a recovery convenience and is not a substitute for the client’s responsibility to maintain its client-owned repository and backups.

Restoration from an available Greykhat archive may be billable. Restoration of the retained original deliverable is included for clients with an active software support agreement.

The project agreement defines archive availability, retention, security, restoration, and deletion terms. Live production passwords, private keys, API secrets, and client data are excluded from archival source-code repositories; configuration templates contain no live secrets.

New capabilities, feature additions, major upgrades, platform changes, and expanded integrations are treated as additional work. They are reviewed, scoped, and quoted as a new phase unless explicitly included in an active support agreement.

Corrections for defects discovered after launch are handled according to the warranty and acceptance terms defined in the project contract.

Client-controlled environment

Greykhat can deploy the application into compatible infrastructure controlled by the client. The client maintains ownership of the relevant hosting accounts, subscriptions, domains, and production data.

Greykhat-managed environment

Hosting, monitoring, backups, maintenance, and technical support are available through an optional annual software support agreement.

The support agreement defines

  • Hosting responsibilities
  • Backup frequency and retention
  • Monitoring
  • Included maintenance
  • Security updates
  • Support availability
  • Recovery expectations
  • Usage limits
  • Third-party costs
  • Application and data transfer when the agreement ends

Uptime, recovery, and response commitments apply only when they are explicitly defined by the annual agreement.

Ways to build and support your software

Choose the engagement that matches the work.

Discovery determines whether the right next step is hourly work, a defined project, an iterative roadmap, or ongoing support.

The goal is not to create more software. It is to give the business a maintainable system that supports the work more effectively than the spreadsheets, plugins, and manual processes it replaces.

Every engagement includes defined scope, visible progress, testing, practical documentation, a client-owned source repository, and a clear plan for deployment and post-launch support.

Has your business outgrown its current tools?

Describe the system you wish existed.

Tell Greykhat how the work happens today, where the current tools fall short, and what a better system would allow your team or customers to accomplish.

Initial discovery consultations are complimentary and time-limited. Complex end-to-end solutions may require a separate paid discovery and planning engagement before development can be accurately scoped.

Schedule a software discovery call