Terms

1. Who you're dealing with

Blakelike Consulting is run by Blake Sichel in California, USA (“I”, “me”). You can reach me at bsichel@blakelike.com or (707) 494-1841. By using this site you agree to these terms.

2. Using this site

• The site describes my services and past work. It's general information, not professional, legal, or financial advice.
• Demos and prototypes (for example /pitlane-demo, /polecat-demo, /doheny-demo) show how something works. They use fake or sample data, may be incomplete, and are not the clients' live systems.
• Please don't try to break, overload, or scrape the site, or use it for anything unlawful.
• The site's design, text, and code are mine. Client names, logos, screenshots, and content belong to their owners and are shown as examples of my work. If you own something shown here and want it changed or taken down, email bsichel@blakelike.comand I'll handle it promptly.

3. How projects work

• Written scope first. No work starts and no payment is due until you've accepted a written proposal or statement of work covering scope, price, timeline, and payment terms.
• Prices on this site are starting points (“from $500”, etc.), not offers. Your quote depends on scope.
• Timelines are estimates. Most builds take one to three weeks, but timing depends on scope and on getting what I need from you (content, access, feedback).
• Changes to scope after we start are quoted separately before I do them.

4. Payment

Payment amounts and due dates are set in your proposal and invoices. If a payment is late, I may pause work until it's settled. Refunds are covered in the Refund Policy.

5. Monthly retainers

If you choose an optional monthly retainer, its price, what it includes, and its billing date are set in writing before it starts. It renews monthly until you cancel. You can cancel any time by email to bsichel@blakelike.com; cancellation takes effect at the end of the month you've already paid for, and you won't be charged again.

6. Who owns the work

• Once you've paid in full, you own the custom code, designs, and content I create specifically for your project, and I'll hand over the source code and access.
• Third-party and open-source software, fonts, images, and services used in your project stay under their own licenses and terms, which you agree to follow.
• I keep ownership of my general tools, templates, know-how, and pre-existing code, and give you a permanent license to use any of it that's built into your project.
• I may list your business name and show non-confidential screenshots of the work in my portfolio unless you tell me in writing not to. I never publish your private data.

7. How I use AI

I use AI tools (such as Claude) to help write code and drafts. I review, test, and stand behind everything I deliver. AI output can still contain mistakes, so please review deliverables before relying on them, especially anything legal, financial, medical, or safety-related.

8. Your responsibilities

• Give accurate information and the access and content the project needs.
• Only send me content and data you have the right to use.
• Make sure your use of what I build follows the laws that apply to your business: privacy notices for data you collect, consent before you text or email people, disclosing chatbots to your customers, and industry rules such as HIPAA if you handle health information.

9. Warranties

I fix bugs in what I built, at no charge, during the support (“hypercare”) period stated in your proposal. Otherwise, the site, demos, and deliverables are provided “as is”, without other warranties, to the extent the law allows. I don't guarantee specific business results such as revenue, rankings, or time saved.

10. Limits on liability

To the extent the law allows, I'm not liable for indirect or consequential losses (such as lost profits or lost data), and my total liability for any claim about a project is limited to the amount you paid me for that project in the three months before the claim. Nothing here limits liability that can't be limited by law.

11. Third-party services

Projects often run on outside services (hosting, databases, email, payment, AI APIs). Their outages, price changes, and terms are outside my control, and you may need your own accounts with them.

12. Governing law

These terms are governed by the laws of the State of California. Before anything formal, let's try to sort out any problem by talking it through; if we can't, disputes go to the state or federal courts located in California.

13. Changes

I may update these terms; the effective date at the top shows the latest version. Changes don't affect a signed proposal unless we both agree.