These terms apply to your use of miqrodesign.com, the intake form, and any communication (email, SMS, phone) between you and Miqrodesign. Your project's build contract, if you sign one, overrides anything here that conflicts with it.

1. What we are

Miqrodesign is a product line of Miqro Inc, a Kansas domestic for-profit corporation. We build websites, internal tools, and automation layers for small- to mid-sized businesses. "We" / "us" refers to Miqro Inc (operating as Miqrodesign). "You" refers to the person or business submitting the intake form or engaging us.

2. Acceptable use

• Don't submit information that isn't yours or that you don't have permission to share.
• Don't try to exploit, scrape, or reverse-engineer the application.
• Don't use our services for anything illegal, for spam, or for content that violates third-party rights.

3. SMS communications (TCPA / 10DLC)

We do not send marketing broadcasts. We do not share your phone number with third parties for their marketing purposes. Carrier opt-out keywords (STOP, UNSUBSCRIBE, CANCEL, END, QUIT) are honoured automatically and recorded in our suppression list within one business hour.

4. Voice calls

We may place phone calls to you regarding your project. If a call is recorded, you will be told so verbally at the start of the call. You may decline recording by hanging up or asking us to stop recording; we will honour the request or end the call. Recordings are retained for 90 days.

5. Intellectual property

The Miqrodesign brand, site code, and internal tooling belong to Miqro Inc. Work products we deliver to you under a signed project contract transfer to you on final payment, as stated in that contract. Until final payment, we retain ownership and the right to withhold delivery.

6. Marketing materials, pricing, and the binding contract

Every page on this website — including the landing page, /pricing, /work, /about, /faq, /contact, and any tier descriptions, feature lists, screenshots, dashboards, or example outputs — is marketing material, not a contractual offer. It describes the kinds of work Miqrodesign typically performs and the ranges those engagements typically fall into.

Specifically, nothing on this site constitutes a binding promise as to:

• Final scope, deliverables, or specific features
• Final price, payment schedule, or out-of-pocket third-party costs
• Timelines, launch dates, or completion windows
• Performance characteristics of any agent, automation, dashboard, or integration shown or described
• Continuity of any feature, integration, or third-party dependency
• Specific business outcomes (revenue, conversions, hires, cost reductions, etc.)

The signed project proposal and contract — countersigned by both Miqro Inc and the client — is the only document that creates binding commitments on scope, price, schedule, acceptance criteria, and deliverables. Where this site and the signed contract disagree, the contract controls. Where this site is silent and the contract is silent, no obligation is owed.

If there is no signed contract, no obligation to pay exists and no work is guaranteed.

7. How an engagement actually runs

Engagements that proceed to a signed contract follow this order of operations. Nothing is signed and no money moves until we meet in person or by video to review the proposed contract together. Nothing earlier than step 4 creates an enforceable commitment.

1. Intake. Prospect submits the form at miqrodesign.com/start. Submission is not an offer or an acceptance.
2. Quote drafted from intake. We use the intake to draft an exploratory proposal — estimated price ranges, target timeline, recommended path, and a draft of the contract that would govern the engagement. This document is emailed to the prospect ahead of the review meeting. It is an estimate, not an offer; it does not bind either side.
3. Contract review meeting. We meet in person or by video to walk through the proposed scope, price, acceptance criteria, and contract clauses together. The prospect can request changes; we either accept them on the call or come back with a revised draft. We do not ask for, accept, or rely on a signature before this meeting happens.
4. Signed contract + deposit (the binding gate). After the review meeting (at the meeting or within the validity window stated on the proposal, typically 14 days), both sides sign and the deposit invoice is paid. Until both events occur, either side can walk away with no penalty and no fee owed.
5. Development. We build against the scope written into the signed contract. Requests outside that scope require a written change order: a short addendum stating the additional work, the additional price, and the timeline impact. Change orders take effect only when both sides countersign.
6. Internal QA. We test deliverables against the acceptance criteria written into the contract before delivering for review.
7. Acceptance review. Client reviews against the same acceptance criteria. The client either (a) signs the acceptance form, or (b) lists material defects that fail acceptance criteria. We fix listed defects and re-present. Cosmetic preferences not in the acceptance criteria are handled by change order.
8. Final payment + handover. On signed acceptance, the final invoice is due per the contract's payment terms. Source code, design files, account access, and documentation transfer on receipt of final payment. Engagement either ends or rolls into a separately-signed retainer.

If a prospect asks us to skip the review meeting and sign asynchronously, we decline. The meeting is how we confirm both sides understand the same scope and acceptance criteria. No exceptions.

8. No warranty

This website and any free-tier tooling are provided "as is", without warranty of any kind, express or implied, including without limitation any warranty of merchantability, fitness for a particular purpose, or non-infringement. We do our best to keep things working and secure; we do not promise zero downtime, zero bugs, or specific outcomes from any example agent, automation, or integration shown on the site. Warranties applicable to paid engagements are set out in the signed project contract, not on this page.

9. Forward-looking statements about agents and automation

Miqrodesign and Miqromanage marketing copy describes capabilities of AI agents, automation pipelines, and operations layers. Those descriptions reflect the configurations we have built or are building and the behaviors we expect from them. They are not performance guarantees. Agent behavior depends on third-party model providers (Anthropic, Moonshot, Groq, Google), third-party integrations (Twilio, Resend, Stripe, Supabase, Railway, GitHub, etc.), data quality, and prompt configuration — any of which can change without notice and may affect output quality, latency, or availability. Specific agent behaviors that matter to your business must be written into the signed proposal as acceptance criteria; otherwise they are illustrative only.

10. Limitation of liability

To the maximum extent permitted by law, Miqro Inc's aggregate liability for any claim relating to the website, marketing materials, or unpaid services is limited to one hundred US dollars (USD $100). For paid engagements, liability is limited as stated in the signed project contract — typically, the fees paid in the twelve months preceding the claim. In no event is Miqro Inc liable for indirect, incidental, consequential, special, exemplary, or punitive damages, including lost profits or lost business opportunity, even if advised of the possibility.

11. Governing law

These terms are governed by the laws of the State of Kansas, USA. Any dispute will be brought in the state or federal courts located in Johnson County, Kansas.

12. Changes

We may update these terms. Significant changes will be announced by email to contacts on our list. Continued use of the site or services after a change constitutes acceptance.

13. Contact

Miqro Inc (Miqrodesign)
Kansas, United States
hello@miqrodesign.com