Every question we hear, answered plainly.

Fixed-price packages range from $250 to $7,120, depending on the service and the package level. Each service page shows its prices, and the pricing page lists every service and package in one place. Custom projects are priced in a written quote that states the scope, price and delivery window before you pay.

The first level covers one workflow, built and tested end to end. The second adds branching and exception handling, so unusual cases are handled instead of failing. The third adds monitoring, alerts and reconciliation, so a silent failure becomes a visible one. A custom quote covers setups of your own that do not fit a package.

Through our secure hosted checkout, in US dollars. You can pay by major credit or debit card, Apple Pay, Google Pay or PayPal, plus other local methods where they are available in your country. The exact options appear at checkout. We never see your full card number. See the payment terms for the detail.

In full before work starts, for fixed-price services. Payment is what starts the project: you are redirected to your customer dashboard, and the first milestone begins. Custom projects may use milestones instead, each listed in your quote with the event that triggers it, and work on the next milestone starts after the previous one is paid.

Prices exclude taxes unless stated. Where tax applies, for example VAT or sales tax in some places, it is calculated at checkout and shown before you pay, so there is no surprise on your card statement. If you have a tax number that changes the treatment, tell us before you pay so it is handled correctly.

Yes. A receipt is emailed to you at payment and is also kept in your dashboard, and we issue a formal invoice with your company’s legal name, address and tax number on request. Ask through your dashboard or the contact form under ‘Billing, invoice or payment’ and include the details to print.

14 days from the date we send it. After that, we re-confirm availability and scope before you approve, because platform plans, your requirements and our schedule can change. If you need more time, tell us and we will usually extend it.

The smallest fixed-price package starts at $250. There is no separate minimum beyond that, no setup fee and no admin fee. If your need is smaller than a package, ask through the contact form; sometimes the honest answer is a native setting that you can switch on yourself.

The number of systems involved, the complexity of the exceptions and the amount of testing all differ. A simple one-way sync costs less than a two-way sync with refunds, retries and reconciliation, because the second one has far more ways to go wrong and each needs designing and proving. The service page states exactly what each price covers.

No. Packages and quotes are fixed-price for a stated scope, so you know the total before you pay and an unexpected problem does not raise it. If we find something outside the agreed scope, we tell you before doing extra work, and you decide whether to add it.

No. There is no setup fee, admin fee or cancellation fee. The price you accept is the price you pay for the stated scope. Platform subscriptions and plan upgrades are paid directly to those platforms, and we tell you in advance if a project needs a plan with API access.

Yes. Stripe, Notion, HubSpot and the other tools keep their own plans and are billed by their owners. Our price covers the design, build, testing and handover of the automation. If your plan lacks something the automation needs, such as API access, we tell you before you order.

Prices are in US dollars. Your card issuer, wallet or payment provider may show a converted amount at its own rate, which is outside our control and can differ slightly between providers. The amount we receive and invoice is the dollar price you accepted.

Ask through the contact form. For larger custom projects we can often arrange an alternative that our payment providers support, such as a bank debit or an invoice paid through a supported method. Fixed-price services are normally paid at checkout by card, wallet or PayPal.

Yes, as a custom quote. Choose ‘Several automations together’ on the quote form and describe each one. Connected workflows often share access, testing and documentation, which we reflect in a single scope and price. We do not advertise a standard discount, because the saving depends on the work.

No. An accepted order keeps its price, even if our prices change later. Changes to the scope are quoted before any work on them, and you approve them or decline them. The total you agreed is the total you pay.

Yes, in full, any time before work starts, with nothing deducted. Once work has started, refunds are no longer available, though billing errors are always corrected and we refund the service fee if we cannot deliver the agreed scope. The refund policy defines exactly when work is considered started.

When we first review your systems, ask for or receive access, build or test anything, or begin any other task for your order. Reading your brief does not count. If you are unsure whether work has begun, ask through the contact form with your order reference and we will tell you honestly where it stands.

No. If you are eligible, you receive the full amount you paid. We do not deduct processing fees, administration charges or a cancellation fee, and we start the refund within 24 hours of confirming that work has not started.

We correct billing errors in full at any time, whether or not work has started. That includes a duplicate charge, an incorrect amount and a charge you did not authorize. Tell us through the contact form with your order reference and the details, and contact us before opening a dispute with your bank so we can fix it quickly.

We start the refund within 24 hours of confirming that you are eligible. After that, how quickly the money appears depends on your bank or payment provider; banks usually post it within 5 to 10 business days. The refund goes back to the original payment method.

Back to the original payment method, through the same provider you paid with, whether that was a card, PayPal or a wallet. We cannot send a refund to a different card or account, because that is a common route for fraud. If the original card has expired or been replaced, your bank can usually still route the money to the new one.

We complete the work you paid for, including the two included revision rounds and the 30-day correction period. We do not refund after work has started, because the time is reserved and spent on your order. The one exception is if we find that we cannot deliver the agreed scope, in which case we tell you promptly and refund that service’s fee.

We tell you promptly, explain what is blocking the work, and refund the fee for that service. This can happen when a platform plan turns out not to allow what the scope needs. Before refunding, we will offer alternatives such as a smaller scope or a different approach, and you choose, but a refund is always your right in that situation.

Yes, before the next billing period starts, and the cancellation takes effect at the end of the period you have paid for. Periods that have already started are not refunded, because the support time is reserved. Tell us through your dashboard or the contact form, and we confirm in writing.

Open the contact form, choose ‘Refund or cancellation request’ as the topic and include your order reference and the email you paid with. We reply within 24 hours to confirm whether work has started, and if it has not, we start the refund immediately. The refund checker on the policy page shows where your order stands.

A quote is free and has nothing to refund. You pay only when you approve it, and until then, nothing is charged and no work has started. If you decide not to go ahead, simply let it expire after 14 days, or tell us and we will close it.

Our services are designed for businesses. If you are a consumer with mandatory cancellation or refund rights where you live, those rights are preserved and are not reduced by our terms. If you believe they apply to you, tell us through the contact form and we will handle your request under the law that protects you.

From two to twenty-four business days, depending on the service and package. The window is shown on each service page or stated in your quote, so you know it before you pay. The clock starts when payment is received, the brief is complete and the access we need is in place, and your dashboard shows each milestone with a countdown.

Monday to Friday. We work and answer messages every day of the year, but delivery windows are counted in business days so that they are easy to plan around and mean the same thing to everyone. Public holidays are not subtracted, because they differ by country, and we usually work through them anyway.

When three things are true: payment has been received, your brief is complete and the access we need is in place. Until then we may be preparing, but the delivery window has not started. If access is slow, the dashboard shows what is outstanding, and the clock starts the moment the last piece arrives.

Sometimes. Tell us your date when you request a quote, and we will say whether we can meet it, what it depends on and whether it changes the price. Deadline work displaces other projects, so we quote it plainly. We never promise a date that we cannot meet just to win an order.

Slow access approval, platform outages or app review queues, scope changes and missing test data are the usual causes. We tell you as soon as we know, show the effect on the date in your dashboard and continue with everything that does not depend on the delay. If a delay is on our side, it does not pause the clock.

The delivery clock pauses after five business days of waiting on you, for example for access or an answer, and restarts the day we hear from you. Before that, the window is unaffected. We tell you in your dashboard when something is waiting on you, so a delay never comes as a surprise.

You receive a handover message in your dashboard with the documentation and a short test checklist, and the milestone is marked complete. The checklist walks you through checking each route yourself. Delivery also starts your 30-day correction period, during which anything that does not match the accepted scope is fixed free.

Yes. We operate every day of the year, and messages are answered on weekends and public holidays. What differs is how delivery windows are counted: they are stated in business days, Monday to Friday, so that the date you are given is realistic. Work may well be completed sooner than the window suggests.

Yes, on the delivery and turnaround page. Pick a start date and a delivery window, and it counts the weekdays and shows the expected date. It runs in your browser, stores nothing, and counts Monday to Friday only, matching how our windows are defined.

At each milestone, and whenever we need a decision from you. They arrive in your customer dashboard, with an email notification, and each milestone has a countdown so you can see progress without asking. If you want more frequent updates, ask for them on the quote form or in a dashboard message.

A correction period that starts the day we deliver. During it, anything that does not match the accepted scope is fixed at no charge, and fixes do not use up a revision round. Report a problem through a support request in your dashboard with what you expected, what happened and any error message, and we acknowledge within 24 hours.

No. The 30 days run from delivery and do not stop or extend for pauses. If something is waiting on you near the end of the period, tell us before it expires and we will look at it first. We can also quote ongoing support if you want cover for longer.

Only through your secure customer dashboard at boldbellows.com/customer-dashboard, never by message, form or email. Where a platform offers invitations or app authorization, we use those instead and you never share a password at all. If anyone claiming to be us asks for a password anywhere else, do not send it, and tell us.

The narrowest set of permissions that does the job, usually read access first and write access only for the objects the automation changes. Exactly what depends on the platform, so the access and requirements page lists it by platform type, and every request appears in your dashboard with the reason.

Working copies are deleted 90 days after handover unless you ask us to remove them sooner. During the project, data is kept in private storage and shared only with the people on your order. After deletion, the only records we keep are the business records of the order, such as the receipt and the scope, for accounting.

No. Your data, and anything inside your systems that we handle, is used only to build, test and support your automation. It is never used to train artificial intelligence models, ours or anyone else’s. The data processing agreement states this as a commitment.

No, and we do not claim to be. Those certifications are costly audits of larger organizations, and implying one that we lack would be misleading. Instead, we describe our practices openly on the security page, so your team can judge them directly, and we answer written security questionnaires as best we can.

Yes. Our data processing agreement applies automatically to every order, with no signature needed. It covers instructions, confidentiality, security measures, sub-processors, breach notice within 72 hours, audits and deletion. If your compliance team needs a signed copy, ask and we will send one.

After payment you are redirected to log in to your secure customer dashboard. Every access request appears there with the platform, the permission and the reason; enter the key in that request. Never email it, paste it into a form or send it in a file. Our forms will stop a message that looks like it contains a key.

Send them the access guide. It lists exactly what we need and why, platform by platform, so they can approve with confidence. We can also put a short written request in your dashboard for them to attach to their ticket, so the approval is traceable.

Yes. You can remove a user, disconnect an app authorization or rotate a key in the platform whenever you like, and nothing we have built depends on you asking us first. Your handover document lists every permission we used and how to remove it, so ending access at the end of a project takes minutes.

Almost never. We ask for the narrowest role or scope that does the job, and prefer a dedicated user or an app authorization over an administrator account. If a platform truly leaves no alternative for a required action, we tell you which action, why it needs elevated rights and what we will do with them, so you can decide whether to proceed or choose a different approach.

Files sent through the upload page are checked for their real type, passed privately to the project team and never stored in a public folder. Small uploads are emailed and removed from the server at once; larger ones are held in a private area for up to 30 days. Project files we keep are deleted 90 days after handover.

We notify affected clients without undue delay, and within 72 hours of becoming aware. The notice says what happened, what data was involved, what we have done and what we recommend. We keep a written incident process, so the response does not depend on who is available that day.

Only the people working on your order, and only the parts they need. Other clients never see it. Our service providers, such as hosting and email, process it under written agreements that require them to protect it. The privacy policy lists the categories.

We prefer a sandbox. We build and test against a test mode or a copy first, and moving to live data happens only with your approval, usually for the final checks and go-live. You can see every change in the platform’s audit log, and you can ask us to stay out of live data entirely.

Yes. Builds log their actions and alert on failures, so a problem is visible instead of silent. The handover document explains where to look, what a normal run looks like and what to do when an alert fires. The higher package levels add reconciliation checks that compare the systems regularly.

Use the contact form and choose ‘Report a problem with this website’, then describe what you found without including any sensitive data. We acknowledge within 24 hours, investigate promptly and tell you what we found. We appreciate responsible reports and will not take action against good-faith research.

128 platforms and 26 industries, across 165 categories and 2,349 service pages. Browse the services by platform, or ask about one that is not listed; if it has an API, webhooks or a supported connector, we can often build for it and will say honestly when we cannot.

We say so plainly, before you pay. Every service page lists what the automation cannot do, and we flag plan restrictions such as missing API access or low rate limits in the quote. You can then choose a different approach, a higher plan on the platform or a smaller scope.

During the 30-day correction period we assess the change and fix anything that no longer matches the accepted scope. After that, we quote an update before doing any work. Platform changes are rare but real, and the handover document tells you which behaviors the automation depends on.

Sometimes, through supported connectors, scheduled exports or imports. We tell you honestly if the result would not be reliable enough, because an automation that breaks silently is worse than none. If there is no safe route, we say so and suggest alternatives.

In our resources and guides, which cite each platform’s published documentation, and on every service page for the platforms it connects. Always confirm the current figures in the platform’s own documentation for your plan, because limits change.

Rate limits, API access and features differ by plan, and they decide what is possible and how fast it runs. An automation designed for a high plan may be slow or impossible on a free one. We check your plan during the quote and tell you what to upgrade, if anything, before work starts.

The number of requests a platform allows in a period, such as a few per second or a few hundred per minute. If you go over, requests are rejected or delayed. Automations are designed to stay under the limit with queues, pacing and retries, as the glossary explains.

A message a platform sends to a web address of yours when something happens, such as a payment succeeding. It lets an automation react immediately instead of checking every few minutes. Because webhooks can be delayed, repeated or arrive out of order, a good design checks them rather than trusting them blindly.

Platforms retry when they do not get a quick answer, and networks sometimes deliver a message twice, so duplicates are normal. A good automation recognizes an event it has already handled, using an id, and ignores the repeat. That property is called idempotency, and it prevents double charges and duplicate records.

Yes, usually through their APIs or webhooks, with the logic that links them in between. We map the fields, handle the differences in formats, limits and timing, and test the unusual cases. The result behaves like a native integration that happens to be built for your exact needs.

We choose the approach that fits your platforms, limits and budget, and we state it in the quote. Sometimes a visual tool is right, sometimes custom code is. We explain the trade-offs, including who will maintain it and what it costs to run, so you are not locked into something that does not suit you.

Where a connector is not enough, yes. Custom code gives control over retries, queues and edge cases that visual tools handle poorly. The handover document explains how it works, where it runs and how to change it, so that you or another developer can maintain it.

For small to medium volumes, yes, and many teams run well on them. They have rate limits, size limits and no real transactions, so very high volumes or strict consistency need a proper database. Our guides explain the limits to plan for, and we tell you honestly if your volume is too much.

Where a platform exposes them through an API, yes. We state clearly what an AI step can and cannot guarantee, such as that its output may vary, and we add checks, fallbacks and human review where the cost of a mistake is high. We do not promise outcomes an AI model cannot deliver.

Ask. If the platform has a documented API, we can usually build for it, including popular regional payment, messaging and commerce tools. Tell us the platform, your plan and what you want it to do through the contact form, and we will say what is realistic.

Choose ‘A custom automation that is not listed’ on the quote form and tell us the platform. If it is feasible, we scope it and send a written quote with a fixed price. The catalog lists what we have already designed and tested, but it is not the limit of what we can build.

Two revision rounds and a 30-day correction period. A revision is a batch of changes within the agreed scope, and a correction is a fix for anything that does not match it. You request both in your customer dashboard. The revision policy explains which changes are included and which are new scope.

Anything that does not work as the accepted scope describes at delivery. A route that fails on a case the scope covers, a field that maps to the wrong place or an alert that never fires are defects. A new field or a new tool is not, because that is a change to scope, and we quote it first.

If you are a client, open a support request in your customer dashboard, where it is attached to your order. Otherwise use the contact form. We reply within 24 hours, every day of the year, and tell you what we need if the answer depends on more information.

Yes, quoted separately. Ongoing support can cover monitoring, fixes after platform changes and small updates for an agreed monthly period. Ask on the quote form or by message in your dashboard, and we propose terms in writing before you commit to anything.

We quote it before starting. A new feature is a change to scope, so it gets its own short written price and delivery window, and work begins only when you approve. If it is small and fits inside your revision rounds, we tell you, and it costs nothing.

One batch of changes sent together and delivered together. Collecting your changes into a single request lets us apply and test them at once, which is faster and safer than a trickle of small tweaks. Two rounds are included with every build, requested through your customer dashboard.

No. Corrections to something that does not match the accepted scope are free during the 30-day period and do not count as a round. Revision rounds are for changes you want to make to something that is working as agreed.

Within the 30-day correction period we assess the change and fix what no longer matches the accepted scope. After that, we quote a repair before starting, with a clear explanation of what changed on the platform. Monitoring in the higher packages tells you quickly when something has failed.

Yes. The handover document is written so that you or your team can maintain the automation. Be aware that changes made by others are outside the warranty, because we cannot know what was altered. If you want us to look at it afterwards, we will quote it.

We acknowledge within 24 hours, any day of the year, and often much sooner. The acknowledgment says who is looking at it and what we need, if anything. A request that says something live is broken is looked at first.

No. We work in writing so everything is recorded, searchable and shareable with your team, and we publish no phone number to protect everyone from spam. If you prefer to talk, write to us and explain; for complex questions we can arrange a conversation in writing that stays in your dashboard.

You can still ask for changes and fixes. They are quoted before any work starts, so you decide whether they are worth it. If you would like continuing cover, ongoing support can be added as a separate agreement.

Yes. We serve clients worldwide, in English, across time zones. Prices are in US dollars, payments accept cards, wallets and PayPal, and you can tell us your time zone on the quote form so we reply during your working hours.

A person on our team, through the contact form, your customer dashboard and email replies. We do not publish phone numbers or an address, to keep everyone safe from spam. The person who answers has read your message in full and can speak to the platforms you mentioned.

At boldbellows.com/customer-dashboard. After payment you are redirected to log in. It is where you send login details and API keys, share files, message the team, request revisions and follow your milestones.

Yes, on the site, for quick questions such as whether a service fits or where to find a page. For anything that needs detail or a record, write through the contact form, or through your dashboard if you are already a client.

Yes. Agencies and consultants can deliver what we build for them to their own clients, subject to the terms on the licensing and usage page. Tell us on the quote form that it is for a client, so we can document access and handover for the right party.

If you are a client, upload them in your customer dashboard, where they stay with your order. Otherwise use the secure upload page. Login details and API keys go only through your secure customer dashboard, never through files or messages.

Our terms already include confidentiality for both sides. If your company needs its own NDA, send it through the contact form and we will review it and reply, usually within a few days. Please do not include confidential details in that first message.

Yes. Packages start at $250, and most clients are small and mid-sized businesses. Fixed prices and plain-English scopes are designed so that you know the total before you pay and do not need a technical team to approve the work.

Yes, through custom quotes, a data processing agreement and a documented security approach. We state plainly what we do not hold, such as SOC 2 or ISO 27001 certification, and we answer security questionnaires in writing. Procurement can request a signed agreement.

Yes, in writing. Use the contact form and a person replies within 24 hours with a direct answer. Writing means you get a record you can share with colleagues, and it lets us check the platform details before answering.

We keep discovery short and written. The quote form and the project brief collect what is needed, and we ask follow-up questions only when something is unclear. That keeps the price down and the schedule short.

Often, yes. Describe it on the quote form and say how it is built, where it runs and what is going wrong. We review what exists before quoting and tell you whether to repair it or replace it, since a half-working automation can cost more to patch than to rebuild.

The accepted quote or order, together with our terms, forms the agreement; no separate signature is needed. If your organization needs a different document, such as a master services agreement, ask through the contact form and we will review what you send.

Every one. We work across time zones and answer every day of the year. Tell us yours on the quote form and we reply during your working hours, and your dashboard shows milestone times so you can plan around them.

We share what we can, with client permission. Many automations touch private business information, so we do not name clients without agreement. The testimonials page has what clients say in their own words, and we can sometimes arrange a conversation with a client who has agreed.

What the automation does, what it cannot do, the package levels and prices, the delivery window, what we need from you and answers to common questions. Every service page states its scope in plain English, so you can see exactly what you would get before you pay.

2,349 service pages across 165 categories of services, platforms and industries, and the catalog keeps growing. You can browse by platform, search by name, or compare prices on the pricing page.

Use the search, browse by platform, or describe your setup on the contact form and we point you to the closest service. Each service page lists what is included, so you can check the fit quickly.

Yes. Order each service separately, or request a bundled quote on the quote form so related workflows share access, testing and documentation under one scope. We tell you which route is simpler for your case.

Choose the closest one and tell us the difference in your order notes, or request a custom quote. We confirm in writing what changes in scope and price before you pay, so you never buy something that is not quite right.

We review pages when platforms change something we have documented, and on a regular schedule. If you spot something that looks out of date, tell us through the contact form. The scope and price in your accepted order or quote are what bind us.

The main path of the automation, built and tested end to end. For a payment sync it is the usual case: a payment succeeds, the order is recorded and the team is told. Unusual cases such as refunds or duplicates are added in higher package levels.

Planned behavior for the unusual cases: duplicates, empty fields, refunds, failures and out-of-order events. Instead of stopping or creating bad records, the automation follows rules you have agreed, such as retrying, flagging or skipping with a note.

A check that compares two systems and reports differences, so silent failures become visible. For example, a nightly check can find paid orders that never reached your sheet. It is included in the highest package level and optional on custom quotes.

We describe it on the how it works page. It lists the workflow, every permission used, the keys and webhooks created, how to test it and how to revoke access. Ask on the contact form and we will show you its structure.

The handover document and a short test checklist are included, and they are written for your team. Longer training, such as a written training guide for several people, is quoted separately. Ask on the quote form if you expect to need it.

Yes. Tell us through the contact form. If it is feasible, we scope it and send a written quote, and if many people ask for the same thing we add it to the catalog.

No. We do not sell personal information and we do not share it for advertising. It is used to reply to you, to quote and deliver your work, and to run and protect the site. The privacy policy lists exactly what is collected and why.

To keep everyone safe from spam and scraping. Published addresses are harvested by bots, which buries real messages. The contact form routes every message to a person, and replies come to your inbox so you still have a written record.

24 months, after which they are deleted automatically. Files attached to submissions are removed sooner: small ones as soon as they are emailed, larger ones after 30 days. You can ask us to delete yours earlier through the contact form.

Only a few, for security, chat and checkout. There are no advertising cookies and no cross-site tracking. The cookie policy lists each category, who sets it and how long it lasts.

Use the contact form and choose ‘Privacy or data request’, then tell us what you would like removed. We confirm your identity by replying to the email address you used, and we respond within 30 days, usually much sooner. Some records, such as invoices, must be kept for legal reasons.

We target WCAG 2.2 AA and say plainly that we have not had an independent audit. The site is built with proper headings, labels and keyboard support. See the accessibility statement for what we test and how to report a problem.

Always, with no permission needed. For quoting extracts, the copyright policy explains what is fine: short extracts with a credit and a link back.

Choose ‘Report a problem with this website’ as the topic and tell us the page, what you expected and what happened, plus your device and browser if you know them. A screenshot helps. Accessibility problems have their own topic and are treated as defects, so they are fixed rather than added to a wish list.

Only a one-way hash, which cannot be turned back into the address, and only for spam protection and rate limiting. We use it to tell whether the same visitor is sending many forms, not to identify you.

It uses HTTPS everywhere, layered form protection against bots and strict checks on uploaded files. Payments are handled by the payment providers’ hosted checkouts, so card numbers never touch our site. See the security practices.