Supporting software
Apps, Extensions & Custom Builds
Software built around a defined user and workflow, with explicit permissions, acceptance criteria, ownership, and limits.
Buyer problem
Custom software is useful only when the workflow and responsibility are clear.
A feature list is not a product boundary. The work needs named users, a current workflow, system access, data rules, exception behavior, and evidence that defines an acceptable result.
Jaly may build deterministic software, AI-assisted features, or a combination. The architecture follows the problem and constraints rather than forcing a model into the product.
What the work can include
Defined deliverables, not an open-ended promise.
-
Product and workflow definition
Users, tasks, permissions, inputs, outputs, exceptions, non-goals, and acceptance criteria.
-
Architecture and implementation
The smallest maintainable system that fits the approved environment, provider, deployment, and support constraints.
-
Testing and evidence
Functional, permission, accessibility, failure, and acceptance tests appropriate to the risk and distribution path.
-
Handoff and operations
Repository, documentation, ownership, third-party dependencies, deployment, support, and exit responsibilities as agreed.
Inputs and entry criteria
- A named product and technical owner
- Defined users, workflow, and acceptance examples
- Approved access to target systems and data
- Security, privacy, distribution, and support requirements
Limits and exclusions
- No blanket security, compliance, performance, or platform-approval promise
- No named integration until access and provider behavior are verified
- No autonomous consequential action without an approved human-control design
- Ownership, licensing, hosting, and support depend on the written agreement
FAQ
Frequently Asked Questions
What kinds of software can Jaly build?
Scoped work can include web applications, browser extensions, desktop tools, internal interfaces, and integrations when the users, workflow, systems, and acceptance criteria are clear.
Can AI be added to an existing application?
Potentially. Jaly first assesses the task, data boundaries, provider terms, failure behavior, evaluation examples, and human review. A deterministic feature may be the better fit.
How are browser-extension permissions handled?
Permissions are minimized to the functions in scope, documented for review, and tested against the target browser and distribution requirements.
How are authentication and sensitive data handled?
Architecture is selected after identity, access, data classification, provider, retention, logging, and client security requirements are defined. This page does not certify a specific control set.
What happens after handoff?
Repository access, documentation, deployment ownership, support, licensing, third-party costs, and exit responsibilities are set in the written engagement.