Product fit, account help, and payment-workflow support
Talk to the person building it.
I'm Michael, the founder. Tell me how you collect payments today, what you want to change, or where you need help with an existing job.
Email Michael
hello [at] phasecontract [dot] com
For a fit question, one typical job is enough: the work, the price, and when you collect. For help with an existing job, include its name or ID and what you were trying to do. Please leave out passwords and card or bank credentials.
For policies and formal legal details, see Terms, Privacy, and Legal Notice.
Product fit and roadmap feedback
Bring one representative job. Tell me where payment or communication breaks today, or where PhaseContract still forces you back into text messages or spreadsheets.
Account and payment workflow
Include the workspace or job ID, the approximate time, the payment method involved, and the exact action or status you saw. Never email full card numbers, bank credentials, passwords, or verification codes.
Bug reports
Include the page URL, expected behavior, actual behavior, browser or device, and a screenshot if it does not expose private payment information.
Security disclosures
Use responsible disclosure. Include reproducible steps, affected endpoints, and potential impact. Do not access or retain data that does not belong to you. See OWASP guidance for standard disclosure principles.
More context means less back-and-forth
A fit question is easier to answer with one representative project. A support question is easier to trace with the workspace or job ID, timestamp, current status, and intended next action.