Collaborative Email & Team Communication Platform
Budget: €200 – €500 EUR
We are looking for an experienced development team to build a professional collaborative email and internal communication platform for private business use.
The product should provide functionality and usability comparable to leading collaborative inbox platforms such as Missive. Missive is mentioned only as a functional and quality reference.
We are not requesting copied source code, branding, icons, text, proprietary assets or protected visual elements. The final product must use original code, an original design system and properly licensed assets.
## Platforms
The project must include:
* Desktop web application.
* iOS application as the main mobile priority.
* Shared backend, database and real-time infrastructure.
* Architecture ready for a future Android version.
The iOS app must provide a polished mobile experience and must not be a simple website inside a wrapper.
## Main Features
The platform must include:
* Individual and shared email inboxes.
* Google OAuth, Microsoft OAuth and IMAP/SMTP connections.
* Inbox, Drafts, Sent, Snoozed, Archive and Trash.
* Email threading.
* Reply, Reply All, Forward and new email composition.
* To, CC and BCC.
* Rich-text formatting.
* Attachments, drag and drop, pasted images and inline images.
* Email signatures.
* Quick replies or templates.
* Draft auto-save.
* Read and unread status.
* Search.
* Background email synchronisation.
* Internal comments inside email conversations.
* Direct messages and group chatrooms.
* Team spaces.
* Tasks.
* Meetings.
* Notifications.
* User, team and organisation administration.
* Connected calendars.
Users must be able to manage external emails and internal teamwork in the same workspace without exposing internal comments to external recipients.
## Organisations and Permissions
The system must support multiple organisations.
Each organisation may contain administrators, users, teams, shared inboxes, email accounts, team spaces, chatrooms, signatures and calendars.
Users must only access organisations, teams, inboxes and conversations for which they have permission.
Tenant isolation and permissions must be securely enforced in the frontend and backend.
## Desktop Interface
The desktop application should use a professional multi-column layout.
The left sidebar should include:
* Inbox.
* Drafts.
* Sent.
* Snoozed.
* Archive.
* Trash.
* Activity.
* Tasks.
* Direct messages.
* Chatrooms.
* Team spaces.
* Meetings.
* Settings.
Unread and pending counters must update accurately in real time.
The conversation list should display sender, subject, preview, date, unread status, assignment, attachments and task status.
The main conversation area may contain:
* Incoming and outgoing emails.
* Internal comments.
* Tasks.
* Drafts.
* Attachments.
* Assignment changes.
* Status changes.
* System events.
A right-side panel may display internal chat, participants, assignees, tasks, attachments and conversation information.
## Email Composer
The email composer is a critical part of the project and must be polished and production-ready.
It must support:
* New email, Reply, Reply All and Forward.
* To, CC and BCC.
* Subject.
* Rich-text formatting.
* Lists and links.
* Attachments.
* Drag and drop.
* Pasted images.
* Signatures.
* Templates.
* Draft auto-save.
* Sending and error states.
* Discard confirmation.
Users must be able to access the internal team discussion while preparing an external reply.
Internal comments and external recipients must remain strictly separated.
## Internal Chat
Internal communication should support:
* Text.
* Formatting.
* Mentions.
* Emoji.
* Reactions.
* Attachments.
* Images.
* Editing and deletion, subject to permissions.
* Converting comments into tasks.
* Real-time delivery.
* Read indicators.
Messages from the same participant should be visually grouped.
## Tasks and Meetings
Tasks may be created from conversations, comments, meetings or a dedicated task page.
Tasks should include:
* Title.
* Creator.
* Assignee.
* Creation date.
* Due date.
* Status.
* Related conversation or meeting.
The task page should include pending, completed and all-task filters.
Users should also be able to create meetings with:
* Title.
* Date and time.
* Location.
* Objective.
* Invited users.
* Internal discussion.
* Tasks.
* Attachments.
* Activity history.
## Notifications and Search
Notifications should be available for:
* New email.
* Assignment.
* Mention.
* Internal reply.
* New or completed task.
* Meeting invitation.
* Direct or group message.
Notifications may include in-app, browser and iOS push notifications.
Search should support sender, recipient, subject, message content, internal comments, tasks, assignee, team, inbox, date and read status.
## Administration
Administrators should be able to manage:
* Organisations.
* Users.
* Roles and permissions.
* Teams.
* Shared inboxes.
* Email accounts.
* SMTP and IMAP connections.
* Google and Microsoft connections.
* Signatures.
* Templates.
* Calendars.
* Notifications.
* Security settings.
* Audit information.
Sensitive credentials must be encrypted and securely stored.
## iOS Application
The iOS application must support:
* Viewing inboxes and conversations.
* Reading emails.
* Replying, forwarding and composing.
* Internal comments.
* Mentions.
* Direct and group chat.
* Tasks.
* Meetings.
* Attachments.
* Search.
* Assignments.
* Read and unread management.
* Push notifications.
The app must be optimised for touch, safe areas, mobile navigation and the iOS keyboard.
The developer must assist with signing, TestFlight, push notifications and App Store or private distribution.
## Security and Performance
The platform will process confidential company communications.
The solution must include:
* Secure authentication.
* Role-based access control.
* Strong organisation isolation.
* Encrypted connections.
* Encrypted credentials.
* Secure file uploads.
* Session management.
* Rate limiting.
* Audit logs.
* Backups.
* Account revocation.
* GDPR-conscious architecture.
The application must remain responsive with large inboxes, long conversations, multiple users and many attachments.
Applicants should explain their approach to queues, caching, indexing, background jobs, email synchronisation, monitoring and backups.
## Design Requirements
We require a highly polished B2B interface suitable for intensive daily use.
The design must be original, clean, consistent, accessible, responsive and optimised for desktop and mobile.
Reference screenshots may be shared privately to explain workflows, spacing, information hierarchy and expected quality.
The contractor must not:
* Copy another product screen by screen.
* Extract proprietary code, CSS, icons or assets.
* Copy branding or proprietary text.
* Imply affiliation with another company.
* Use unlicensed materials.
## Deliverables
The final delivery must include:
* Complete web application.
* Complete iOS application.
* Backend services.
* Database schema.
* Original UI design files.
* Complete source code.
* Tests.
* Deployment configuration.
* Technical documentation.
* Security and permissions documentation.
* Staging and production environments.
* Knowledge transfer.
The client must have access to the source-code repositories throughout development.
## Intellectual Property and Confidentiality
All custom work must be original or properly licensed.
The contractor must not copy source code, branding, assets or protected content from Missive or any other product.
All third-party dependencies must be disclosed.
Upon full payment, all transferable rights in the custom project must be assigned to the client.
The selected contractor will sign an NDA and intellectual property assignment agreement.
The contractor may not publish screenshots, share source code, mention the project publicly or use it in a portfolio without written permission.
## Application Questions
Please begin your proposal with:
**COLLABORATIVE INBOX PLATFORM**
Then answer:
1. Have you built an email client or shared inbox before?
2. How would you prevent duplicate emails and incorrect threading?
3. How would you guarantee isolation between organisations?
4. What technology would you use for iOS?
5. What are the main technical risks?
6. Which third-party services would you use?
7. Can you create an original professional UI/UX?
8. Will your team sign an NDA and IP assignment?
9. Will we have repository access from the beginning?
10. Please provide your proposed phases, team, budget and relevant examples.
The product should provide functionality and usability comparable to leading collaborative inbox platforms such as Missive. Missive is mentioned only as a functional and quality reference.
We are not requesting copied source code, branding, icons, text, proprietary assets or protected visual elements. The final product must use original code, an original design system and properly licensed assets.
## Platforms
The project must include:
* Desktop web application.
* iOS application as the main mobile priority.
* Shared backend, database and real-time infrastructure.
* Architecture ready for a future Android version.
The iOS app must provide a polished mobile experience and must not be a simple website inside a wrapper.
## Main Features
The platform must include:
* Individual and shared email inboxes.
* Google OAuth, Microsoft OAuth and IMAP/SMTP connections.
* Inbox, Drafts, Sent, Snoozed, Archive and Trash.
* Email threading.
* Reply, Reply All, Forward and new email composition.
* To, CC and BCC.
* Rich-text formatting.
* Attachments, drag and drop, pasted images and inline images.
* Email signatures.
* Quick replies or templates.
* Draft auto-save.
* Read and unread status.
* Search.
* Background email synchronisation.
* Internal comments inside email conversations.
* Direct messages and group chatrooms.
* Team spaces.
* Tasks.
* Meetings.
* Notifications.
* User, team and organisation administration.
* Connected calendars.
Users must be able to manage external emails and internal teamwork in the same workspace without exposing internal comments to external recipients.
## Organisations and Permissions
The system must support multiple organisations.
Each organisation may contain administrators, users, teams, shared inboxes, email accounts, team spaces, chatrooms, signatures and calendars.
Users must only access organisations, teams, inboxes and conversations for which they have permission.
Tenant isolation and permissions must be securely enforced in the frontend and backend.
## Desktop Interface
The desktop application should use a professional multi-column layout.
The left sidebar should include:
* Inbox.
* Drafts.
* Sent.
* Snoozed.
* Archive.
* Trash.
* Activity.
* Tasks.
* Direct messages.
* Chatrooms.
* Team spaces.
* Meetings.
* Settings.
Unread and pending counters must update accurately in real time.
The conversation list should display sender, subject, preview, date, unread status, assignment, attachments and task status.
The main conversation area may contain:
* Incoming and outgoing emails.
* Internal comments.
* Tasks.
* Drafts.
* Attachments.
* Assignment changes.
* Status changes.
* System events.
A right-side panel may display internal chat, participants, assignees, tasks, attachments and conversation information.
## Email Composer
The email composer is a critical part of the project and must be polished and production-ready.
It must support:
* New email, Reply, Reply All and Forward.
* To, CC and BCC.
* Subject.
* Rich-text formatting.
* Lists and links.
* Attachments.
* Drag and drop.
* Pasted images.
* Signatures.
* Templates.
* Draft auto-save.
* Sending and error states.
* Discard confirmation.
Users must be able to access the internal team discussion while preparing an external reply.
Internal comments and external recipients must remain strictly separated.
## Internal Chat
Internal communication should support:
* Text.
* Formatting.
* Mentions.
* Emoji.
* Reactions.
* Attachments.
* Images.
* Editing and deletion, subject to permissions.
* Converting comments into tasks.
* Real-time delivery.
* Read indicators.
Messages from the same participant should be visually grouped.
## Tasks and Meetings
Tasks may be created from conversations, comments, meetings or a dedicated task page.
Tasks should include:
* Title.
* Creator.
* Assignee.
* Creation date.
* Due date.
* Status.
* Related conversation or meeting.
The task page should include pending, completed and all-task filters.
Users should also be able to create meetings with:
* Title.
* Date and time.
* Location.
* Objective.
* Invited users.
* Internal discussion.
* Tasks.
* Attachments.
* Activity history.
## Notifications and Search
Notifications should be available for:
* New email.
* Assignment.
* Mention.
* Internal reply.
* New or completed task.
* Meeting invitation.
* Direct or group message.
Notifications may include in-app, browser and iOS push notifications.
Search should support sender, recipient, subject, message content, internal comments, tasks, assignee, team, inbox, date and read status.
## Administration
Administrators should be able to manage:
* Organisations.
* Users.
* Roles and permissions.
* Teams.
* Shared inboxes.
* Email accounts.
* SMTP and IMAP connections.
* Google and Microsoft connections.
* Signatures.
* Templates.
* Calendars.
* Notifications.
* Security settings.
* Audit information.
Sensitive credentials must be encrypted and securely stored.
## iOS Application
The iOS application must support:
* Viewing inboxes and conversations.
* Reading emails.
* Replying, forwarding and composing.
* Internal comments.
* Mentions.
* Direct and group chat.
* Tasks.
* Meetings.
* Attachments.
* Search.
* Assignments.
* Read and unread management.
* Push notifications.
The app must be optimised for touch, safe areas, mobile navigation and the iOS keyboard.
The developer must assist with signing, TestFlight, push notifications and App Store or private distribution.
## Security and Performance
The platform will process confidential company communications.
The solution must include:
* Secure authentication.
* Role-based access control.
* Strong organisation isolation.
* Encrypted connections.
* Encrypted credentials.
* Secure file uploads.
* Session management.
* Rate limiting.
* Audit logs.
* Backups.
* Account revocation.
* GDPR-conscious architecture.
The application must remain responsive with large inboxes, long conversations, multiple users and many attachments.
Applicants should explain their approach to queues, caching, indexing, background jobs, email synchronisation, monitoring and backups.
## Design Requirements
We require a highly polished B2B interface suitable for intensive daily use.
The design must be original, clean, consistent, accessible, responsive and optimised for desktop and mobile.
Reference screenshots may be shared privately to explain workflows, spacing, information hierarchy and expected quality.
The contractor must not:
* Copy another product screen by screen.
* Extract proprietary code, CSS, icons or assets.
* Copy branding or proprietary text.
* Imply affiliation with another company.
* Use unlicensed materials.
## Deliverables
The final delivery must include:
* Complete web application.
* Complete iOS application.
* Backend services.
* Database schema.
* Original UI design files.
* Complete source code.
* Tests.
* Deployment configuration.
* Technical documentation.
* Security and permissions documentation.
* Staging and production environments.
* Knowledge transfer.
The client must have access to the source-code repositories throughout development.
## Intellectual Property and Confidentiality
All custom work must be original or properly licensed.
The contractor must not copy source code, branding, assets or protected content from Missive or any other product.
All third-party dependencies must be disclosed.
Upon full payment, all transferable rights in the custom project must be assigned to the client.
The selected contractor will sign an NDA and intellectual property assignment agreement.
The contractor may not publish screenshots, share source code, mention the project publicly or use it in a portfolio without written permission.
## Application Questions
Please begin your proposal with:
**COLLABORATIVE INBOX PLATFORM**
Then answer:
1. Have you built an email client or shared inbox before?
2. How would you prevent duplicate emails and incorrect threading?
3. How would you guarantee isolation between organisations?
4. What technology would you use for iOS?
5. What are the main technical risks?
6. Which third-party services would you use?
7. Can you create an original professional UI/UX?
8. Will your team sign an NDA and IP assignment?
9. Will we have repository access from the beginning?
10. Please provide your proposed phases, team, budget and relevant examples.