Every question deservesa straight answer.

What does the development process look like?

Every Amtal project moves through five phases: Discovery & Strategy, Design & Prototyping, Development & Engineering, Testing & Optimization, and Launch & Evolution. Each phase ends with decisions you can see and approve, so the build is never a black box.

How much does a custom software project cost?

Cost is driven by scope, not a menu. The four biggest drivers are how many workflows must be custom-built, what the system integrates with, its security and compliance requirements, and how much of the experience is bespoke design. Discovery pins these down — and produces a fixed price.

We do not bill against open-ended estimates. Discovery produces a fixed scope, price, and deadline, and we treat all three as promises. You know what the project costs before the build begins, and a start is a promise to finish.

How long does a typical project take?

Timeline follows the same drivers as cost: custom workflow depth, integrations, compliance, and design scope. A focused internal tool and a customer-facing platform with billing, roles, and third-party integrations sit at very different points on the calendar — which is why we commit to a deadline only after Discovery, and then keep it.

Do you work on a fixed price or time and materials?

Amtal works on commitments, not estimates. Discovery produces a fixed scope, price, and deadline that we treat as promises — we do not start what we will not finish. That discipline is possible because the unknowns are engineered out up front, before code is written.

What happens after launch?

Launch is the beginning, not the finish line. Amtal stays on as your team: monitoring, maintenance, optimization, and engineers who still know your codebase years in. The systems we build are meant to outlast the people who commissioned them — and we build like it.

How will we communicate during the project?

You get a dedicated point of contact and regular, candid updates — including the uncomfortable ones. You are always informed and involved as the project moves, never managed. If something threatens the scope, the budget, or the deadline, you hear it from us first.

When is custom software worth it over off-the-shelf?

Off-the-shelf wins when your process matches what the tool already does. Custom is worth it when the workflow is your competitive advantage, when ready-made tools would need heavy workarounds to fit, when integrations define the job, or when the software is the product itself.

The honest test: if adapting your business to the tool costs more than building the tool around your business, custom pays for itself. Discovery is where we make that call with you — including telling you when custom is not the answer.

Native or cross-platform: which is right for my mobile app?

Choose native — Swift for iOS, Kotlin for Android — when the app depends on deep platform capabilities, peak performance, or platform-specific experience. Choose cross-platform — React Native or Flutter — when one codebase serving both stores matters more: faster to ship, simpler to maintain. Most business apps are well served by cross-platform; the exceptions are real but specific.

We build both, so the recommendation is driven by evidence about your app — not by the tool we happen to prefer.

Do I need a Salesforce partner, or can we implement it ourselves?

Standard Sales Cloud with out-of-the-box objects and flows is realistic to self-implement. A partner earns its place when the work involves custom Apex or Lightning Web Components, integrations with outside systems, data migration and cleansing, or multiple clouds working together — the point where configuration becomes engineering.

That line — where configuration becomes engineering — is where most self-implementations stall. It is also exactly the work Amtal does: implementation, custom development, integration, and the administration that keeps the org healthy afterward.