DECHY logo

Ctrl K or / to search, arrows to move, Enter to open

Locations

DECHY for organizations in the United States

DECHY is a global technology company. We serve organizations in the United States remotely, with the same services we provide everywhere: software, AI, automation, integration, cloud, and more. We plan for what is particular to working with US teams from the first conversation.

DECHY works remotely and does not operate a US office. Clients reach us through the contact form, and work runs through written updates and scheduled calls.

  • 1,200+ clients helped
  • Building since 2010
  • 15 services, one team
  • 50+ technologies
The Manhattan skyline and Brooklyn Bridge from above.

At a glance

What we build

DECHY works with organizations in the United States on software, AI, automation, integration, and related services, delivered remotely.

The market

What US technology buyers usually ask for

The United States is a very large and varied market, from startups building a first product to enterprises modernizing systems that are decades old. The work we are asked for most often falls into a few groups: custom software and portals, connecting systems, automating manual processes, and adding AI to existing applications.

Buyers here often compare several suppliers and ask for evidence of how a supplier handles security and delivery. They may send a security questionnaire before a project starts. We answer these plainly, describing what we do, without claiming certifications we do not hold.

Speed to a first working version matters, and so does a path to scale. We usually agree a small first stage that proves the idea, then extend it.

Rules and expectations

Considerations that shape US software projects

Four US considerations that commonly affect software and data projects and how they shape what we build
ConsiderationWhy it mattersWhat it means for the build
State privacy laws There is no single national privacy law for most businesses. Several states, including California, have their own rules on personal data. We design for consent, access, and deletion requests, so the system can meet the strictest rules that apply to you.
Sector rules Health, finance, and education data carry specific requirements, for example health information handled by healthcare organizations. We ask which apply, limit access by role, keep audit logs, and build to the requirements you give us.
Supplier security reviews Larger buyers often ask suppliers to describe their security practices, and may expect independent audit reports. We document how we handle access, secrets, and testing, and answer questionnaires directly.
Accessibility Websites and applications are expected to work for people with disabilities. We build to the web accessibility guidelines and test with keyboard and screen reader.

These points are a starting list, not legal advice. Your own adviser can confirm what applies to your organization.

Systems in use

Tools and payment methods we connect to in the US

  1. Card payments and bank transfers

    Cards and ACH bank transfers are the usual ways to pay online, through providers such as Stripe.

  2. Sales tax

    Sales tax rules differ by state and can depend on where the customer is. We connect stores to tax calculation services instead of coding rates by hand.

  3. Customer systems

    Salesforce and HubSpot are widely used. See connecting customer systems.

  4. Accounting

    Small and mid-sized businesses commonly use QuickBooks or similar tools. We connect orders and invoices to the books.

  5. Sign-in

    Single sign-on through the identity provider your organization already uses, so staff sign in once.

  6. Cloud platforms

    AWS, Azure, and Google Cloud are all in common use, with regions across the country.

Most relevant

Where US teams usually start

Build

Connect and automate

Add intelligence

Run safely

Working together

Working across US time zones

The continental United States spans four time zones, so we agree how to work at the start.

  1. Set the rhythm

    We agree a regular call, with times that suit your team's day, and a place where written updates are posted.

    What it produces

    • Meeting schedule
    • Update channel
  2. Keep decisions in writing

    Decisions, questions, and next steps are written down, so a team in one zone is never waiting for a call in another.

    What it produces

    • Decision log
  3. Release often

    Small, frequent releases let you check progress when it suits you.

    What it produces

    • Release notes
    • Demo access
  4. Plan for support hours

    For systems that must be watched, we agree what is covered and how urgent issues reach us.

    What it produces

    • Support terms

Common questions

Questions from US organizations

Do you have a US office?

No. DECHY is a global company and works remotely. Clients reach us through the contact form, and we arrange calls at times that suit your team.

How do you handle the time difference?

We agree meeting windows, keep decisions in writing, and release in small steps, so work continues whichever zone you are in.

Can you meet our company's security questionnaire?

We answer it honestly, describing what we do. We do not claim certifications we do not hold, and we say if a requirement is beyond what we can offer.

Do you work with state or federal agencies?

Public-sector projects have their own procurement rules. Tell us about the project and we will say whether and how we can take part.

Have a different question?

Tell us what you are weighing up and we will answer it plainly.

Ask a question

Already a client? Email support@dechytech.com

Tell us about your project

Describe what you want to build or fix, and where your team works. We will propose how an engagement would run.