Questions we getbefore a project starts.

Custom software, automations and AI for businesses that outgrew their spreadsheets and off-the-shelf tools: CRMs, websites, mobile apps, internal tools, voice agents and chatbots, and automations that take repetitive work off your team.

If it has to be built around how you work rather than bought as it is, it fits.

Related See our work

The engineers building your product. There is no account manager or salesperson in between, so questions, decisions and changes go straight to the people doing the work.

Yes. Many engagements begin as one tool that solves one bottleneck. If it proves useful, we scope the next piece from there instead of committing you to a full system up front.

No. We work with the people who run the process, and at launch we hand over documentation, recorded walkthroughs and training so your team can use the system day to day.

During the build we mainly need access to the systems we connect to, someone who can explain how the process works today, and timely feedback.

We build around what already works instead of ripping it out. Most projects connect to your existing CRM, spreadsheets or accounting software through their APIs rather than replacing them.

Projects have a fixed price. After discovery you get a written scope with the deliverables, the price, the payment schedule and the dates, and nothing starts until you have agreed to it. No surprise invoices.

Support plans and Voice AI are monthly services. We do not publish a price list because cost depends on what you need; a call is the quickest way to get a number.

Related Terms of Service

It depends on scope. A single internal tool is quicker than a system that touches several teams. As a reference, the plan on our home page is a typical 12-week build, from discovery to launch.

You get the real dates in the written scope before any work starts, not after.

It happens. Anything outside the written scope is quoted first, with what it adds in price and time, and we only do it once you have agreed in writing. The original price does not move on its own.

Every project follows the same five phases, so you always know what is next:

• Discovery: workshops with your team and a written scope with a fixed price and dates.
• Design: flows and screens, reviewed with the people who will use them.
• Build: we build in steps and show you working software along the way.
• Launch: go live, with docs, recorded walkthroughs and training for your team.
• Support: monitoring, fixes and monthly improvements.

That is agreed project by project and written into the scope: what you own, what you receive a licence to use, and what stays with Altamar, such as our own tools and libraries. Your content and data always stay yours.

Raise it on the first call and we will put it in writing before work begins.

Related Intellectual property in our terms

We write documentation as we build, not at the end, and we give your team a walkthrough at launch. Whether someone else can maintain the code depends on the rights set out in your written scope, so tell us early if that matters to you.

You can keep us on a monthly support plan: monitoring, fixes and improvements to what we built. It renews monthly and you can cancel whenever you like; it then ends at the close of the month you have paid for.

Related Cancellation Policy

You contact us directly, not a ticket queue. How fast we aim to respond is set in your support plan, and problems in a live system come before new feature work.

A voice agent that answers and books calls for your business, connected to the tools you already use. It is a monthly service. Where it applies, usage and telephony costs, such as call minutes and phone numbers, are passed through and listed separately in your written scope.

Related What a voice agent can and cannot handle Choosing a voice agent provider

No. It works best for repeatable calls, like questions, bookings and status checks, where a person can step in for anything unusual. We tell you plainly if your use case is not a good fit, and a person should always stay in the loop for high-stakes calls.

Yes. Calls, written scopes and documentation can be in either language, and we build products and voice agents for both. Our terms are published in English and Spanish.

We are a remote team, registered in Wyoming, USA, and we have no office to visit. At the start of a project we agree meeting times that overlap well with yours, and we write things down so work keeps moving between calls.

Yes, on request. We are happy to sign a mutual NDA before you share anything sensitive, and we never name a client or publish results without written approval.

Related Privacy Policy

Book a 30-minute call. You talk to an engineer, describe what your team does by hand today and leave with a clear idea of what to build first. A written scope with a fixed price follows if we both want to go ahead.