What does Kesher Software LLC. do?
We provide custom software development, websites and backend systems, APIs, cloud integration, automation, systems integration and ongoing technical support.
Do you sell ready-made products?
No. We focus on business software and technology services shaped around a client’s workflow.
How does a project start?
Use the contact form or email to share the business goal. We then discuss scope, timing, responsibilities and a suitable next step.
How is pricing prepared?
Pricing is based on agreed scope, complexity, integrations, delivery milestones and support requirements. Contract scope changes are reviewed separately.
Can you work with an existing system?
Yes. We can review an existing codebase or platform, assess risks and propose a practical integration, maintenance or recovery plan.
Who owns the source code?
Ownership follows the signed agreement. Custom deliverables are normally transferred after payment and acceptance, while general reusable know-how remains with Kesher.
How are payments arranged?
Payment milestones are written into the contract. This website does not process card payments.
Do you support deployment?
Yes. Deployment, configuration, migration and handover support can be included in the agreed scope.
What happens after launch?
We can provide warranty support, issue triage, maintenance and planned improvements under the agreed support terms.
How do you protect business information?
We limit collection to the project need, use access controls and document additional confidentiality requirements for regulated work.
Can a non-technical team use the result?
We include operating notes, documentation and training appropriate to the agreed project.
How do I ask a follow-up question?
Email support@keshersoftwarellc.com or submit the Contact form.
Communication and updates
Project communications are normally handled by the named business contacts and the support email. We keep decisions, approvals and changes in a written record so both parties can understand what was agreed. If a policy or project condition changes, we explain the effect on information handling, delivery timing or support responsibilities and identify the date the change takes effect. Written communication helps each party coordinate staff, preserve an accurate project history and resolve questions without relying on memory.
Questions and requests
Requests about privacy, delivery, a service scope, an account or a policy can be sent to support@keshersoftwarellc.com. Please include enough context for us to identify the relevant business relationship without sending unnecessary sensitive information. We may ask for reasonable verification before changing account information or disclosing project records. We aim to acknowledge a clear request within three business days and will provide a practical response or explain what additional information is needed.
Business continuity
We plan work around documented access, backups, release notes and clear ownership. External services, hosting providers and network conditions can affect availability, so project agreements identify the responsibilities that remain with each party. When an incident affects a committed milestone, we communicate the known impact, the next action and an updated expectation. Continuity planning may include alternate communication channels, staged releases, recovery copies and a temporary change freeze while the cause is investigated.
Definitions and scope
In these policies, “Kesher,” “we” and “us” mean Kesher Software LLC. “Client,” “you” and “your” mean the business or individual authorized to discuss a project with us. “Services” include software discovery, design, development, integration, deployment, maintenance, support and related professional work described in a proposal or contract. “Deliverables” include agreed source code, configurations, documentation, reports, training materials and deployed software. These pages describe our general operating rules; a signed contract, statement of work or data processing arrangement controls whenever it contains a more specific requirement.
Records and access
We maintain business records needed to respond to enquiries, administer accounts, deliver contracted work, document approvals and support an audit trail. Access is limited to personnel and service providers who need the information for an assigned responsibility, and access may be removed when that responsibility ends. Client contacts should tell us promptly when an employee changes role or no longer needs access. We may retain invoices, approvals, technical decisions and support history for the period required by contract, accounting practice or applicable law. When retention is no longer required, records are deleted, anonymized or securely disposed of according to the nature of the material.
Operational responsibilities
Each party is responsible for the information, permissions and decisions it controls. Clients should provide accurate business requirements, nominate an authorized approver, protect their credentials and review proposed releases within the agreed review window. Kesher is responsible for performing the contracted work with reasonable care, documenting material assumptions, reporting known risks and preserving the agreed acceptance evidence. A delay caused by missing access, late feedback, unavailable third-party systems or a change in direction may require a revised schedule. We will describe the dependency and proposed adjustment so the parties can make an informed decision.
Changes and effective dates
We may revise a policy when our services, technology, legal obligations or operating practices change. The current version is published on this website with an effective date or a clear indication of the latest update. Changes normally apply prospectively and do not reduce a party’s rights under a signed agreement unless the parties expressly agree to amend that agreement. For an active project, we will use the agreed communication channel to highlight a material change that could affect delivery, data handling, support or fees. If you have a question about which version applies, contact us before relying on a provision.