Frequently asked questions
Answers about working with Accordax: process, pricing, source-code ownership, technology choices, timelines and support after launch.
- How do we start working together?
- Send us a short description of your project through the contact form. We reply within one business day, arrange a call to understand your goals, and then send a written proposal with scope, timeline and cost.
- Do you sign an NDA before discussing my idea?
- Yes. We're happy to sign your NDA or provide our own before you share any confidential details.
- What information do you need for an estimate?
- Your goals, who the users are, the main features you have in mind, any systems we need to connect to and your target launch date. A rough list is enough — we'll help turn it into a clear scope.
- How much does a website or app cost?
- It depends on scope, integrations and design complexity. After our first call we give you a fixed quote for well-defined projects, or a monthly estimate for ongoing work, so there are no surprises.
- Do you work fixed price or time and materials?
- Both. Fixed price suits projects with a clear scope; time and materials or a dedicated team suits evolving products. We'll recommend the model that fits your situation — see our Pricing page for details.
- Who owns the source code?
- You do. Once invoices are paid, the source code, designs and documentation are yours, and everything is kept in a repository you control.
- How involved do I need to be?
- We ask for a named contact who can answer questions and attend a short demo every two weeks. Between demos you can follow progress in a shared project board.
- How long does a typical project take?
- A company website usually takes 4–8 weeks, a web or mobile application 8–16 weeks, and larger enterprise systems are delivered in phases. We agree milestones up front.
- How do you ensure quality?
- Every change is code-reviewed and covered by automated tests, and we test on real devices and browsers before each release. You review and accept each milestone.
- Which technologies do you use?
- Mostly ASP.NET Core and C# on the server, Angular and TypeScript on the web, and Flutter or native Swift/Kotlin for mobile — hosted on Azure or AWS. We also work with PHP and existing systems when a project needs it.
- Can you take over or improve an existing system?
- Yes. We start with a code and architecture review, fix the most urgent risks and then improve the system step by step without disrupting your business.
- What happens after launch?
- We offer support and maintenance plans covering monitoring, security updates, backups and small improvements, with agreed response times.
- Do you provide hosting?
- We set up and manage hosting on the cloud platform that suits you, in your own account so you stay in control, and we can manage it for you on an ongoing basis.
- Is it easy to add an AI chatbot to our website or app?
- A focused chatbot that answers from your own documents is one of the quickest AI projects: typically 4–8 weeks to a production-ready first version. Most of the effort goes into preparing good source content, deciding what the bot may answer, testing it on real questions and connecting it to your systems — not into the AI model itself.
- Can you add AI features to our existing .NET application?
- Yes. We add features such as natural-language search, summaries, classification or an assistant to existing ASP.NET, Angular and mobile applications, using Microsoft.Extensions.AI and Semantic Kernel so the rest of your system doesn't need to change.
- Is our data safe when we use AI?
- We design for it: data stays in your own cloud subscription (for example Azure OpenAI), is not used to train public models, and the assistant only sees what the signed-in user is allowed to see. We also log prompts and responses so you can audit usage.
- Will an AI chatbot make things up?
- We reduce that risk by grounding answers in your documents, showing the sources, instructing the model to say when it doesn't know, and handing off to a person. Before launch we test the assistant against a set of real questions and keep monitoring answer quality afterwards.
- What does it cost to run AI features?
- Running costs depend mainly on usage volume and the model chosen. We estimate them up front, add caching and usage limits, and pick the smallest model that meets your quality bar, so costs stay predictable.