Questions we get on the first call. All of them.
Grouped by topic. Each question also lives on the page it belongs to; the link next to it takes you there.
General
- What do you build?
- Custom software with an AI part that does real work. Document processing, email triage, data extraction, matching, generation, internal tools, and full products built around one of those. We do not build marketing automation, outbound systems or chatbots with no data behind them.
- Where are you, and how do time zones work?
- You contract with Infinity Systems LLC, a US company registered in Wyoming, and pay in US dollars. We work on Central European Time, from Serbia. For US clients that means a shared window of 9:00 to 13:00 Eastern, and work delivered while you sleep. EU, UK and Swiss clients share our full working day.
Pricing
- How does pricing work?
- Every build is a fixed-price sprint. You get a written quote with a price and an end date after a 30-minute call and a one-page brief. The quote covers the written scope. If we underestimated, we absorb it. Scope changes get a new written quote before we start on them.
- Who is this not for?
- Builds under $10,000, hourly staff augmentation, enterprise procurement with RFPs and security questionnaires before a scoping call, regulatory certification as a deliverable, payment in equity or on success, and lead generation or outbound systems.
- What is the payment schedule?
- Feature and Product Sprints are paid in three parts, 30% at signing, 40% at the mid-sprint demo, 30% at production deploy. Platform Sprints are paid in four parts, 30%, 30%, 20%, 20%. We invoice in US dollars; euros on request.
- What does the Continuous Build retainer cover?
- A fixed number of build days each month, weekly releases, a roadmap call, hosting and monitoring operations, dependency updates and model cost reporting. The Full plan adds on-call for production incidents. First term is three months, then month to month with 30 days' notice.
- What happens if the scope grows during a sprint?
- We log every new idea in a visible "next" list. Anything that must ship inside the sprint gets a written change quote before we start on it. Everything else becomes the first roadmap of the retainer.
- What moves a quote toward the top of a range?
- More integrations, more user roles, migration from an existing system, a security review, and AI workflows that need their own evaluation data set. Fewer of these move it toward the bottom.
- Why do you show price ranges and not one price?
- Because scope differs. The range tells you where a build of that kind lands. Your quote is one number, in writing, before work starts.
Process
- What happens after the fix window ends?
- Most clients continue on a Continuous Build retainer, which starts while the fix window is still open, so there is no gap. If you stop, you keep everything and can hire anyone else to continue. There is no lock-in to break.
- How long does a build take?
- A Feature Sprint takes 2 to 4 weeks, a Product Sprint 4 to 8 weeks, a Platform Sprint 8 to 12 weeks. The end date is on the quote. We show you working software every week.
- What does the week-one exit mean in practice?
- After the first weekly demo you can stop. You pay only the signing deposit, which covers that week, and you keep everything built so far, including the repository and the accounts in your name.
- What does "in production" mean to you?
- Deployed on your cloud account, monitored, documented, with a runbook, and used by real people with real data. A demo is a milestone. Production is the finish line.
- What do you need from us each week?
- One person who can make decisions, about two hours a week for the demo and questions, access to the systems we integrate with, and sample data early. The faster the answers, the faster the build.
AI and stack
- Which AI models do you use, and are we locked in?
- We choose the model per task, by quality and cost, and keep the model layer behind one interface so it can be swapped. Model accounts are yours from day one. Nothing in the build ties you to one vendor.
- Can you use our stack instead?
- Often, yes. If your system is TypeScript, Python or a mainstream cloud, we work inside it. If it is something else, we say so on the first call and quote accordingly or recommend someone else.
- Who writes the code, people or AI?
- Both. AI coding agents write most of the code. The founder designs the architecture, writes the hard parts, reviews every change, and is on every call. Every change ships with tests and goes through a review gate before it reaches your repository.
- Why this stack?
- Because we have shipped with it and can support it. TypeScript end to end keeps one language across the product. Postgres is boring in the right way. The AI layer is isolated so a model can be swapped without touching the product.
Guarantees and legal
- What does "in your name" mean for accounts?
- The repository, the cloud account, the model API accounts and the domain are created under your organisation at kickoff. We work inside them with the access you grant. When we leave, you revoke our access. Nothing moves.
- How is the fixed price protected?
- The statement of work lists the scope. The price covers that scope. Our estimation errors are ours. Only a written change order you approve can change the price.
- Do you sign NDAs?
- Yes, within 24 hours of a request. You do not need one for the first call. We talk about the problem, not your secrets.
- What is not covered by the guarantees?
- Changes you make to the system after handover, third-party outages, and costs of your own accounts such as cloud or model usage. The fix window covers defects in what we built, as described in the statement of work.
Contact
- Should I book a call or send a brief?
- Send a brief if you already know what you want built. Book a call if you want to talk it through first. Both lead to the same written quote.
- How fast do you reply?
- First reply within one business day. A written estimate within three business days of receiving your brief.
Services
- How much manual work has to exist for this to pay off?
- As a rule of thumb, from about 20 hours a week of repetitive reading, typing or routing. Below that, the fixed price takes longer to earn back and we say so on the call. On this page
- What data do you need from us?
- A sample of real cases, 100 or more, with the correct outcome where you have it. Access to the systems the workflow reads from and writes to. We sign an NDA first if you want one. On this page
- What happens when the model is wrong?
- Low-confidence cases go to a review queue, a person decides, and the decision becomes training data for the evaluation set. The system gets more precise with use, and nobody loses a case to a silent error. On this page
- Can it run inside our existing tools?
- Usually. We integrate with the inbox, ERP, CRM or storage you already use. If a tool has no API, we tell you on the first call and quote the workaround. On this page
- What is the difference from a platform?
- An internal tool serves one team and reads data you already have. A platform serves many customers or teams, or replaces a system you run on, often with a data migration. Platforms are a Platform Sprint from $50,000. On this page
- Can it connect to the tools we already use?
- Usually, yes. If a system has an API or a database we can reach, the tool can read from it and write to it. We check the connections before quoting. On this page
- Who maintains it after launch?
- You own the code and the accounts, so anyone can. Many clients keep us on a Continuous Build retainer for changes and new screens. On this page
- Is 4 to 8 weeks enough for a real MVP?
- For a focused product, yes. The sprint has one core feature, up to four roles, payments and admin. What it does not have is a second product idea. We cut scope on the first call, in writing, and the quote reflects it. On this page
- Do I need a designer?
- A designer joins the sprint for one to two weeks for the product's key screens and a small design system. It is in the price. On this page
- Should I start with a proof of concept?
- If the core of the product is uncertain, for example whether a model can read your documents well enough, yes. A proof of concept answers that in 2 to 4 weeks, before you pay for a full product. On this page
- Can you take over after launch?
- Yes. Most clients continue on a Continuous Build retainer with the same people, a weekly release and a roadmap call. It starts while the fix window is still open. On this page
- Why does a Platform Sprint need a paid Scoping Review first?
- Because migration and integrations hide surprises. The Scoping Review is five days, $1,500, and ends with a written scope, an architecture sketch, a risk list and a fixed quote. It is credited against the sprint if you sign within 30 days. On this page
- Can we keep using the old system during the build?
- Yes. The new system is built alongside, migration is rehearsed on a copy, and the cutover is one planned step with a rollback. On this page
- Who is on the team?
- The founder leads and reviews everything. A part-time second engineer, a designer for the key screens, and an external security reviewer join for the parts that need them. Agents do the volume. On this page
- What about our data and compliance?
- The system runs on your cloud account in the region you choose. We build GDPR-aware and HIPAA-aware systems; the certification itself stays with you, and we say that plainly. On this page
- Native apps or one codebase?
- One codebase for iOS and Android is the default, because it halves the work and the apps still feel native. If your product needs something only native code can do, we say so before quoting. On this page
- Who publishes the apps?
- You do, under your own Apple and Google developer accounts. We prepare the builds, the store listings and the review submission, and we handle what the reviewers ask for. On this page
- We already have an MVP. Can you build on it?
- Usually, yes. We review the code in the Scoping Review first. If it is a good base, we build on it; if it is not, we say so and quote the rebuild. On this page
- Is there a smaller option?
- Yes. If you need a first version to test the market, an MVP is a Product Sprint from $25,000 in 4 to 8 weeks. On this page
- What if the answer is no?
- Then you have spent a small, fixed amount instead of a full build, and you get a written result that says why and what would need to change. That is a good result too. On this page
- Is the prototype thrown away?
- Not usually. The code is yours, and when the answer is yes, the full build starts from the parts that worked. On this page
- Does it have to involve AI?
- No. A proof of concept can test anything risky, such as an integration, a data migration or a performance limit. AI questions are the most common ones. On this page
Industries
- Have you built finance software for a client?
- Not yet, and we say so on this page. The invoice intake agent is a sample build, a practice project with no client, that shows how we would approach it. On this page
- Which accounting systems can you connect to?
- Any system with an API or an import format. We check yours on the first call and name the integration in the quote. On this page
- How do we know the extracted numbers are right?
- Rules check totals, tax and supplier details on every invoice, and the evaluation set measures accuracy on your past invoices before launch. Anything that fails a rule or scores low goes to a person. On this page
- Have you built healthcare software for a client?
- Not yet, and we say so on this page. The clinic booking app is a sample build, a practice project with no client, that shows how we would approach it. The first clinic gets an honest quote and a case study it can approve. On this page
- Is the software HIPAA compliant?
- We build HIPAA-aware systems, with access control, audit logs, encryption and data kept on your accounts. A vendor that handles protected health information is a business associate under HIPAA, so we sign a business associate agreement with you before any patient data enters the system. Your compliance lead decides what else the system needs. On this page
- Will the AI give medical advice?
- No. The systems we build sort, summarise and draft. Anything that touches a clinical decision is shown to a member of your staff, who decides. On this page
- Have you built legal or compliance software for a client?
- Not yet, and we say so on this page. The compliance document platform is a sample build, a practice project with no client, that shows how we would approach it. On this page
- How do you stop the model from making things up?
- The model may answer only from the approved documents it is given, and must cite them. Answers without a source are not shown, and the evaluation set includes questions the documents cannot answer, to check that the system says so. On this page
- Does the software give legal advice?
- No. It finds, compares and summarises your own documents. The decisions stay with your lawyers and compliance staff. On this page
- Have you built logistics software for a client?
- Not yet, and we say so on this page. The field service dispatch system and the logistics control tower are sample builds, practice projects with no client, that show how we would approach them. On this page
- How are delays predicted?
- With a classic model trained on your past trips, not a language model. It gives a time and a range, and it is checked every week against what really happened. A language model writes the short reason and drafts the message to the customer, and a person sends it. On this page
- Can customers see their own shipments?
- Yes. A customer portal shows each customer only its own shipments, documents and exceptions. Access is enforced in the data layer, not only in the screens. On this page
- Have you shipped this for a law or accounting firm?
- Not yet, and we say so on this page. The document workflows are the same ones we build elsewhere. The first firm gets an honest quote and a case study it can approve. On this page
- Is our data used to train anything?
- No. Model accounts are in your name with training opt-out, and the evaluation sets we build stay in your repository. On this page
- Can the system make decisions on its own?
- Not the ones that matter. Anything with legal, financial or client-facing effect goes through a review step. The model drafts and sorts; a person decides. On this page
- Have you built real estate software before?
- Not for a client yet, and we say so on this page. The first agency gets an honest quote and a case study it can approve. On this page
- Can you integrate with our listing portal or CRM?
- If it has an API or an export, yes. We check that on the first call and name it in the quote. On this page
- What about photos and floor plans?
- Models can now read floor plans and tag photos reliably. Both are typical Feature Sprint scope. On this page
Answers and comparisons
- Which documents work well?
- Documents that arrive often and carry the same kinds of fields, even when the layout changes. Invoices, purchase orders, delivery notes, claims, applications and standard contracts are good fits. A document type you see ten times a year is usually not worth automating. On this page
- Do we need training data?
- You need real documents, not a labelled training set. We collect a sample of your recent documents, including the messy ones, and record the correct fields for each. That sample becomes the evaluation set that every change is measured against. On this page
- What happens when a field is read wrong?
- The system scores how sure it is about each field. Low scores and rule failures go to a review queue, where a person fixes the value. Each fix is logged, and recurring mistakes go into the evaluation set. On this page
- What is a build day?
- One founder-directed day of agent and human capacity. The founder plans and reviews the work, AI coding agents and contractors do the volume, and the result ships in the weekly release. On this page
- Can we start with a retainer instead of a sprint?
- No. The retainer is sold only after a sprint, so it starts on a system we built and know. It begins while the sprint's fix window is still open, so there is no gap between launch and the next release. On this page
- Is a fixed price always more expensive?
- It carries a margin for the builder's risk, so a perfectly estimated hourly project would cost a little less. Perfectly estimated hourly projects are rare. Most fixed-price buyers pay less in total because scope and date are decided before work starts. On this page
- What should a fixed-price quote contain?
- The scope in plain language, what is explicitly out, the end date, what "done" means, the payment schedule, the fix window, who owns the code and accounts, and how a change is priced. If any of these is missing, it is not a fixed price. On this page
- How do you handle changes?
- New ideas go on a visible list. Anything that must ship inside the sprint gets a written change quote before we start on it. Everything else becomes the first retainer roadmap. On this page
- Can we use US model providers under the GDPR?
- Yes, with the usual safeguards for transfers outside the EU. These are a processor agreement, a transfer mechanism such as the EU-US Data Privacy Framework or standard contractual clauses, and settings that keep your data out of model training. Several providers also offer EU data processing. Your data protection officer decides which setup fits. On this page
- Is our AI software high-risk under the AI Act?
- Most business tools are not. High-risk uses are listed in the Act and include areas such as hiring, credit scoring, education and access to essential services. If your software makes or shapes decisions in one of those areas, get legal advice before the build, because the obligations are much larger. On this page
- Who is the data controller?
- You are, for your customers' and employees' data. The cloud and model providers act as processors under your accounts, with processor agreements between you and them. Infinity Systems works inside those accounts, so we are a processor too and sign a data processing agreement with you. On this page
- What makes an MVP take longer than 8 weeks?
- Three things. A second product idea added mid-sprint. Integrations with systems that have no API. Decisions that wait more than a day. The first two are cut or quoted in writing before the sprint; the third is on both of us. On this page
- Can it be faster than 6 weeks?
- One AI feature on an existing product, yes, 2 to 4 weeks. A full MVP with accounts, payments and admin cannot be done well faster than six, and we do not quote it that way. On this page
- When do I see something working?
- At the end of week one. You see the AI core on your data with a first accuracy number, and you can stop there and keep the work. On this page
- Is an AI agent more expensive than a chatbot?
- Usually, yes. A chatbot that answers questions from your documents reads and replies. An agent also acts in your systems, for example it creates tickets or updates records, so it needs integrations, permissions and a review step for risky actions. That work, not the model, is most of the price. On this page
- Can we test an agent on our data before paying for production?
- Yes. A proof of concept runs the agent on your real data for 2 to 4 weeks and measures how often it is right. It is priced as a Feature Sprint, so you know the cost before you start. On this page
- Why is one AI feature $10,000 and not $5,000?
- Because the feature is in production, not in a demo. The price covers integration with your systems, a review queue, an evaluation set on your real data, deployment on your cloud, monitoring and 30 days of fixes. The model call itself is the cheap part. On this page
- Do agencies charge more or less?
- Agencies typically bill $50 to $150 an hour with teams of 2 to 10 people and no fixed date. A 12-week project with three people at $75 an hour is about $108,000, open-ended. Freelancers charge less but cannot take a platform-sized build alone. On this page
- What about the cost of the AI itself?
- Model usage is billed by the provider on your own account. A document workflow processing a few thousand items a month costs tens of dollars. A product with heavy generation can reach a few hundred. We measure it in the first week and show you the number. On this page
- Is an evaluation set the same as training data?
- No. Training data teaches a model. An evaluation set only tests it. We rarely train models for business software; we pick a model, write the instructions, and use the evaluation set to prove the result works on your cases. On this page
- Who decides what the right answer is?
- You do. We draft the expected answers from your past decisions and records, and someone on your team who does the work today checks them. Where two people would disagree, we write down the rule. On this page
- What happens when the score drops?
- The change does not ship. A drop means a new prompt, model or code change made some cases worse. We look at which cases failed, fix the cause, and run the set again. On this page
- What should the contract say about ownership?
- That the code and other work created for you are assigned to you, that the repository and accounts are in your name, and what happens to access when the work ends. Without a written assignment, the person or company who wrote the code can keep the copyright in many countries, including the US. On this page
- Can AI-generated code be copyrighted?
- In the US, the Copyright Office protects the parts a person wrote, selected or arranged, not material produced by an AI on its own. Code built with AI coding agents is designed, reviewed and edited by people, but if copyright in specific code matters to you, ask a lawyer about your case. On this page
- Who owns what the model produces for our users?
- The business terms of the major model providers give the output to the customer, which is you, because the model accounts are in your name. Check the current terms of the provider you use; we show you which ones apply during the build. On this page
- Is a small team with AI agents really as fast as an agency?
- For builds of this size, faster, because there is no hand-off chain. Agents write the volume, the founder reviews every change, and decisions take hours, not meetings. For a programme needing twenty people, no, and we say so. On this page
- What is the risk of a small team?
- Capacity. We publish a capacity rule, at most three engagements at once, and the week-one exit means you can leave early with everything if the fit is wrong. On this page
- Why not just hire?
- A hire takes three to six months to find and costs salary before anything ships. A sprint ships in that time. Many clients do both. The sprint builds the first version, and the hire takes it over with our handover. On this page
- Is a freelancer cheaper?
- For small tasks, yes. For a full build, compare totals, not rates. An hourly project has no ceiling, while a fixed price does. Add the cost of your own time spent managing and reviewing the work. On this page
- Is Infinity Systems a freelancer with a company name?
- No. The founder designs and reviews, AI coding agents write most of the code, and contractors join for specialist work. The contract is with a US company, Infinity Systems LLC, and the guarantees are written into every statement of work. On this page
- Can our new hire take over the code?
- Yes. The repository, accounts and documentation are in your name from day one, and every system ships with a runbook. The handover is a working session with your engineer, not a negotiation. On this page
- Should we build first or hire first?
- If the product idea is still being tested, build first. A shipped first version shows what skills the product needs, which makes the hire easier. If the software is already your core business, hire, and use a sprint for a well-defined piece of it. On this page
- Can you take over a workflow we built in a no-code tool?
- Yes. A working no-code version is a good brief. It shows the steps, the data and the edge cases. We rebuild it as code on your accounts and add the evaluation set and review queue. On this page
- When does a no-code tool get expensive?
- When volume grows and the tool charges per task, or when you need an integration it does not have. Compare the monthly bill at your expected volume with the one-time build plus your own running cost. On this page
- Which hours, contract and hosting apply?
- We work on Central European Time, with 9:00 to 13:00 Eastern shared with US clients. The contract is with Infinity Systems LLC, a Wyoming company, and the system runs on your cloud account in the region you choose. On this page
- Is a lower hourly rate cheaper in the end?
- Not always. With hourly billing the total depends on how many hours the team needs, how much rework there is and how much of your time goes into managing it. A fixed price puts a ceiling on the total. On this page
- Why is a fixed price safer than an agency estimate?
- Because the builder carries the estimation risk. If an hourly project takes longer, you pay for the extra hours. If our fixed-price build takes longer, we absorb it. Scope you add later is quoted separately, in writing. On this page
- Can a small team handle a platform-sized build?
- Up to 8 to 12 weeks and $100,000, yes. That is the Platform Sprint. Contractors join on demand for specialist work. Beyond that size, an agency or an in-house team is the better shape, and we say so on the first call. On this page
Book a call, or send the brief. A written price in three working days.
No NDA needed for the call. We sign one within 24 hours if you want it.
Not sure about the budget? Estimate your price in six questions